forked from extern/nushell
649c8319e6
* Add input and output types to $nu.scope.commands This commit changes the schema: instead of command.signature: table we now have command.signatures: list<table> with one signature for every input-output type pair. * Represent signatures as a map from input_type to signature * Sort signature entries * Drop command name from signature tables * Don't use "rest" as name of rest parameter; use empty string instead * Bug fix: was creating records with repeated keys E.g. $nu.scope.commands | where name == 'hash sha256' | get signatures.0 | table -e $nu.scope.commands | where name == 'transpose' | get signatures.0 | table -e |
||
|---|---|---|
| .. | ||
| nu_plugin_custom_values | ||
| nu_plugin_example | ||
| nu_plugin_gstat | ||
| nu_plugin_inc | ||
| nu_plugin_python | ||
| nu_plugin_query | ||
| nu-cli | ||
| nu-color-config | ||
| nu-command | ||
| nu-engine | ||
| nu-glob | ||
| nu-json | ||
| nu-parser | ||
| nu-path | ||
| nu-plugin | ||
| nu-pretty-hex | ||
| nu-protocol | ||
| nu-system | ||
| nu-table | ||
| nu-term-grid | ||
| nu-test-support | ||
| nu-utils | ||
| old | ||
| README.md | ||
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.