mirror of
https://github.com/nushell/nushell.git
synced 2025-05-28 22:07:40 +02:00
f2169c8022
# Description In conflict with the documentation, the msgpack serializer for plugins is actually using the compact format, which doesn't name struct fields, and is instead dependent on their ordering, rendering them as tuples. This is not a good idea for a robust protocol even if it makes the serialization and deserialization faster. I expect this to have some impact on performance, but I think the robustness is probably worth it. Deserialization always accepts either format, so this shouldn't cause too many incompatibilities. # User-Facing Changes This does technically change the protocol, but it makes it reflect the documentation. It shouldn't break deserialization, so plugins shouldn't necessarily need a recompile. Performance is likely worse and I should benchmark the difference. # Tests + Formatting - 🟢 `toolkit fmt` - 🟢 `toolkit clippy` - 🟢 `toolkit test` - 🟢 `toolkit test stdlib`
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.