nushell

mirror of https://github.com/nushell/nushell.git synced 2025-05-07 00:12:58 +00:00

History

Allow int input when using a formatstring in into datetime (#13541 )

# Description

When using a format string, `into datetime` would disallow an `int` even
when it logically made sense. This was mainly a problem when attempting
to convert a Unix epoch to Nushell `datetime`. Unix epochs are often
stored or returned as `int` in external data sources.

```nu
1722821463 | into datetime -f '%s'
Error: nu:🐚:only_supports_this_input_type

  × Input type not supported.
   ╭─[entry #3:1:1]
 1 │ 1722821463 | into datetime -f '%s'
   · ─────┬────   ──────┬──────
   ·      │             ╰── only string input data is supported
   ·      ╰── input type: int
   ╰────
```

While the solution was simply to `| to text` the `int`, this PR handles
the use-case automatically.

Essentially a ~5 line change that just moves the current parsing to a
closure that is called for both Strings and Ints-converted-to-Strings.

# User-Facing Changes

After the change:

```nu
[
  1722821463
  "1722821463"
  0
] | each { into datetime -f '%s' }
╭───┬──────────────╮
│ 0 │ 10 hours ago │
│ 1 │ 10 hours ago │
│ 2 │ 54 years ago │
╰───┴──────────────╯
```

# Tests + Formatting

Test case added.

- 🟢 `toolkit fmt`
- 🟢 `toolkit clippy`
- 🟢 `toolkit test`
- 🟢 `toolkit test stdlib`

# After Submitting

2024-08-05 20:05:32 -05:00

src

Allow int input when using a formatstring in into datetime (#13541 )

2024-08-05 20:05:32 -05:00

tests

Path migration part 4: various tests (#13373 )

2024-08-03 10:09:13 +02:00

Cargo.toml

Bump version to 0.96.2 (#13485 )

2024-07-29 17:20:55 -07:00

LICENSE

Fix rest of license year ranges (#8727 )