Devyn Cairns 01d30a416b Change PluginCommand API to be more like Command (#12279) ... # Description This is something that was discussed in the core team meeting last Wednesday. @ayax79 is building `nu-plugin-polars` with all of the dataframe commands into a plugin, and there are a lot of them, so it would help to make the API more similar. At the same time, I think the `Command` API is just better anyway. I don't think the difference is justified, and the types for core commands have the benefit of requiring less `.into()` because they often don't own their data - Broke `signature()` up into `name()`, `usage()`, `extra_usage()`, `search_terms()`, `examples()` - `signature()` returns `nu_protocol::Signature` - `examples()` returns `Vec<nu_protocol::Example>` - `PluginSignature` and `PluginExample` no longer need to be used by plugin developers # User-Facing Changes Breaking API for plugins yet again 😄		2024-03-27 11:59:57 +01:00
..
from	Change PluginCommand API to be more like Command (#12279)	2024-03-27 11:59:57 +01:00
lib.rs	Reorganize plugin API around commands (#12170)	2024-03-14 16:40:02 -05:00
main.rs	Add support for engine calls from plugins (#12029)	2024-03-09 11:26:30 -06:00