forked from extern/nushell
9fcc49e556
cc/ @stormasm # Description i was about to start the cratification of the 0% commands and thought i could refactor and simplify a bit the declaration of the `bits` commands, having hopefully a simpler structure to work with the other commands 😌 this PR: - gives real names to all the `bits` commands, instead of `SubCommand` - make them publicly available inside the `nu-cmd-extra` crate to declare them through `add_extra_decls` - move the declaration code to the top-level `mod.nu` of `nu-cmd-extra` so that all commands can be declared there as in `default_context` in `nu-command` # User-Facing Changes ``` $nothing ``` # Tests + Formatting - 🟢 `toolkit fmt` - 🟢 `toolkit clippy` - ⚫ `toolkit test` - ⚫ `toolkit test stdlib` # After Submitting ``` $nothing ```
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.