nushell/crates/nu-command/src/date
Darren Schroeder 66e5e42fb1
report which datetime couldn't be converted (#7980)
# Description

This PR will help report a bad date that can't be converted where the
error message says `* Unable to parse datetime`. This is helpful when
you're converting a big table and it fails somewhere that you really
can't see. I put it in `[]` so that when it's null, you can see that
there should be something there.

Before:
```
> 'Tue 1 0' | into datetime 
Error: nu:🐚:datetime_parse_error (link)

  × Unable to parse datetime
   ╭─[entry #1:1:1]
 1 │ 'Tue 1 0' | into datetime
   · ────┬────
   ·     ╰── datetime parsing failed
   ╰────
  help: Examples of supported inputs:
         * "5 pm"
         * "2020/12/4"
         * "2020.12.04 22:10 +2"
         * "2020-04-12 22:10:57 +02:00"
         * "2020-04-12T22:10:57.213231+02:00"
         * "Tue, 1 Jul 2003 10:52:37 +0200"
```
After:
```
> 'Tue 1 0' | into datetime
Error: nu:🐚:datetime_parse_error (link)

  × Unable to parse datetime: [Tue 1 0].
   ╭─[entry #4:1:1]
 1 │ 'Tue 1 0' | into datetime
   · ────┬────
   ·     ╰── datetime parsing failed
   ╰────
  help: Examples of supported inputs:
         * "5 pm"
         * "2020/12/4"
         * "2020.12.04 22:10 +2"
         * "2020-04-12 22:10:57 +02:00"
         * "2020-04-12T22:10:57.213231+02:00"
         * "Tue, 1 Jul 2003 10:52:37 +0200"
```

# User-Facing Changes

New format for the error message.

# Tests + Formatting

Don't forget to add tests that cover your changes.

Make sure you've run and fixed any issues with these commands:

- `cargo fmt --all -- --check` to check standard code formatting (`cargo
fmt --all` applies these changes)
- `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A
clippy::needless_collect` to check that you're using the standard code
style
- `cargo test --workspace` to check that all tests pass

# After Submitting

If your PR had any user-facing changes, update [the
documentation](https://github.com/nushell/nushell.github.io) after the
PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-06 14:17:07 -06:00
..
date_.rs Add extra_usage messages for subcommand-only commands (#7594) 2022-12-24 07:16:29 -06:00
format.rs report which datetime couldn't be converted (#7980) 2023-02-06 14:17:07 -06:00
humanize.rs report which datetime couldn't be converted (#7980) 2023-02-06 14:17:07 -06:00
list_timezone.rs Use imported names in Command::run signatures (#7967) 2023-02-05 22:17:46 +01:00
mod.rs Add 'date to-record' (#5058) 2022-04-01 21:09:30 +13:00
now.rs Use imported names in Command::run signatures (#7967) 2023-02-05 22:17:46 +01:00
parser.rs Port date commands to engine-q 2021-10-31 07:54:51 +01:00
to_record.rs report which datetime couldn't be converted (#7980) 2023-02-06 14:17:07 -06:00
to_table.rs report which datetime couldn't be converted (#7980) 2023-02-06 14:17:07 -06:00
to_timezone.rs report which datetime couldn't be converted (#7980) 2023-02-06 14:17:07 -06:00
utils.rs report which datetime couldn't be converted (#7980) 2023-02-06 14:17:07 -06:00