forked from extern/nushell
# Description To my knowledge `type@completer` annotations only make sense in arguments at the moment. Restrict the parsing. Also fix a bug in parsing the completer annotation should there be more than 1 `@` - Add test that we disallow completer in type - Guard against `@` inside command name - Disallow custom completers in type specification # User-Facing Changes Error when annotating a variable or input-output type with a completer # Tests + Formatting Tests to verify the error message
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.