Stefan Holderbach 95b78eee25 Change the usage misnomer to "description" (#13598) ... # Description The meaning of the word usage is specific to describing how a command function is *used* and not a synonym for general description. Usage can be used to describe the SYNOPSIS or EXAMPLES sections of a man page where the permitted argument combinations are shown or example *uses* are given. Let's not confuse people and call it what it is a description. Our `help` command already creates its own *Usage* section based on the available arguments and doesn't refer to the description with usage. # User-Facing Changes `help commands` and `scope commands` will now use `description` or `extra_description` `usage`-> `description` `extra_usage` -> `extra_description` Breaking change in the plugin protocol: In the signature record communicated with the engine. `usage`-> `description` `extra_usage` -> `extra_description` The same rename also takes place for the methods on `SimplePluginCommand` and `PluginCommand` # Tests + Formatting - Updated plugin protocol specific changes # After Submitting - [ ] update plugin protocol doc		2024-08-22 12:02:08 +02:00
..
diff.rs	Fix #12280: replace difference crate with similar (#12282)	2024-03-25 21:13:12 -05:00
fake_persistent_plugin.rs	Allow plugins to report their own version and store it in the registry (#12883)	2024-06-21 06:27:09 -05:00
fake_register.rs	Split the plugin crate (#12563)	2024-04-27 12:08:12 -05:00
lib.rs	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00
plugin_test.rs	Add and use new Signals struct (#13314)	2024-07-07 22:29:01 +00:00
spawn_fake_plugin.rs	Split the plugin crate (#12563)	2024-04-27 12:08:12 -05:00