mirror of
https://github.com/nushell/nushell.git
synced 2025-08-16 06:07:52 +02:00
Bugfix/into datetime ignores timezone with format (#15370)
Close #15119 when this is merged # Description > Note: my locale is +1 **Before the changes 🔴**  See the issue for more detailed description of the problem. **After the changes 🟢**  # User-Facing Changes The ``into datetime`` command will now work with formatting and time zones or offset together # Tests + Formatting Fmt + clippy OK **Note about the tests I added**: those tests don't really test my changes, as they were already passing before my changes. Nevertheless I thought I could push them # After Submitting I don't think anything is necessary
This commit is contained in:
@ -18,4 +18,4 @@ A base crate is one with minimal dependencies in our system so that other develo
|
||||
|
||||
### Background on nu-cmd-lang
|
||||
|
||||
This crate was designed to be a small, concise set of tools or commands that serve as the *foundation layer* of both nu and nushell. These are the core commands needed to have a nice working version of the *nu language* without all of the support that the other commands provide inside nushell. Prior to the launch of this crate all of our commands were housed in the crate *nu-command*. Moving forward we would like to *slowly* break out the commands in nu-command into different crates; the naming and how this will work and where all the commands will be located is a "work in progress" especially now that the *standard library* is starting to become more popular as a location for commands. As time goes on some of our commands written in rust will be migrated to nu and when this happens they will be moved into the *standard library*.
|
||||
This crate was designed to be a small, concise set of tools or commands that serve as the *foundation layer* of both nu and nushell. These are the core commands needed to have a nice working version of the *nu language* without all of the support that the other commands provide inside nushell. Prior to the launch of this crate all of our commands were housed in the crate *nu-command*. Moving forward we would like to *slowly* break out the commands in nu-command into different crates; the naming and how this will work and where all the commands will be located is a "work in progress" especially now that the *standard library* is starting to become more popular as a location for commands. As time goes on some of our commands written in rust will be migrated to nu and when this happens they will be moved into the *standard library*.
|
||||
|
Reference in New Issue
Block a user