mirror of
https://github.com/nushell/nushell
synced 2024-12-26 04:53:09 +00:00
02313e6819
# Description The help description on `transpose --header-row/-r` appears to be wrong (and now that I understand that, it probably explains why it's confused me for so long). It currently says: ``` -r, --header-row - treat the first row as column names ``` This just looks wrong - The first **row** of the input data is not considered. It's the first **column** that is used to create the header-row of the transposed table. For example: To record using `-dr`: ```nu [[col-names values ]; [foo 1 ] [bar 5 ] [baz 7 ] [cat -12 ] ] | transpose -dr ╭─────┬─────╮ │ foo │ 1 │ │ bar │ 5 │ │ baz │ 7 │ │ cat │ -12 │ ╰─────┴─────╯ ``` To table using `-r`: ```nu [[col-names values ]; [foo 1 ] [bar 5 ] [baz 7 ] [cat -12 ] ] | transpose -r ╭───┬─────┬─────┬─────┬─────╮ │ # │ foo │ bar │ baz │ cat │ ├───┼─────┼─────┼─────┼─────┤ │ 0 │ 1 │ 5 │ 7 │ -12 │ ╰───┴─────┴─────┴─────┴─────╯ ``` # User-Facing Changes Updates the help description to: ``` -r, --header-row - use the first input column as the table header-row (or keynames when combined with --as-record) ``` # Tests + Formatting - 🟢 `toolkit fmt` - 🟢 `toolkit clippy` - 🟢 `toolkit test` - 🟢 `toolkit test stdlib` # After Submitting N/A |
||
---|---|---|
.. | ||
nu-cli | ||
nu-cmd-base | ||
nu-cmd-extra | ||
nu-cmd-lang | ||
nu-cmd-plugin | ||
nu-color-config | ||
nu-command | ||
nu-derive-value | ||
nu-engine | ||
nu-explore | ||
nu-glob | ||
nu-json | ||
nu-lsp | ||
nu-parser | ||
nu-path | ||
nu-plugin | ||
nu-plugin-core | ||
nu-plugin-engine | ||
nu-plugin-protocol | ||
nu-plugin-test-support | ||
nu-pretty-hex | ||
nu-protocol | ||
nu-std | ||
nu-system | ||
nu-table | ||
nu-term-grid | ||
nu-test-support | ||
nu-utils | ||
nu_plugin_custom_values | ||
nu_plugin_example | ||
nu_plugin_formats | ||
nu_plugin_gstat | ||
nu_plugin_inc | ||
nu_plugin_nu_example | ||
nu_plugin_polars | ||
nu_plugin_python | ||
nu_plugin_query | ||
nu_plugin_stress_internals | ||
nuon | ||
README.md |
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.