nushell/crates/nu-explore/src
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
..
commands Change the usage misnomer to "description" (#13598) 2024-08-22 12:02:08 +02:00
nu_common Add and use new Signals struct (#13314) 2024-07-07 22:29:01 +00:00
pager Clean up key event handling (#13574) 2024-08-09 18:07:50 -07:00
registry Change the usage misnomer to "description" (#13598) 2024-08-22 12:02:08 +02:00
views explore: pass config to views at creation time (#13312) 2024-07-07 08:09:59 -05:00
default_context.rs Move explore command out of nu-command deps (#9421) 2023-06-14 01:18:36 +02:00
explore.rs Change the usage misnomer to "description" (#13598) 2024-08-22 12:02:08 +02:00
lib.rs Add top-level crate documentation/READMEs (#12907) 2024-07-14 10:10:41 +02:00