forked from extern/nushell
154856066f
# Description See also: #9743 Before: `http <subcommand> -H` took a list in the form: ```nushell [my-header-key-A my-header-value-A my-header-key-B my-header-value-B] ``` Now: In addition to the old format, Records can be passed, For example, ```nushell > let reqHeaders = { Cookie: "acc=barfoo", User-Agent: "Mozilla/7.0 (Windows NT 33.0; Win64; x64) AppleWebKit/1038.90 (KHTML, like Gecko)" } > http get -H $reqHeaders https://example.com ``` is now equivalent to ```nushell http get -H [Cookie "acc=barfoo" User-Agent "Mozilla/7.0 (Windows NT 33.0; Win64; x64) AppleWebKit/1038.90 (KHTML, like Gecko)"] https://example.com ``` # User-Facing Changes No breaking changes, but Records can now also be passed to `http <subcommand> -H`. # Tests + Formatting # After Submitting
Nushell core libraries and plugins
These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.
Foundational libraries are split into two kinds of crates:
- Core crates - those crates that work together to build the Nushell language engine
- Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.
Plugins are likewise also split into two types:
- Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
- Extra plugins - these plugins run a wide range of different capabilities like working with different file types, charting, viewing binary data, and more.