forked from extern/nushell
8403fff345
related to https://discord.com/channels/601130461678272522/601130461678272524/1134079115134251129 # Description before 0.83.0, `print` used to allow piping data into it, e.g. ```nushell "foo" | print ``` instead of ```nushell print "foo" ``` this PR enables the `any -> nothing` input / output type to allow this again. i've double checked and `print` is essentially the following snippet ```rust if !args.is_empty() { for arg in args { arg.into_pipeline_data() .print(engine_state, stack, no_newline, to_stderr)?; } } else if !input.is_nothing() { input.print(engine_state, stack, no_newline, to_stderr)?; } ``` 1. the first part is for `print a b c` 2. the second part is for `"foo" | print` # User-Facing Changes ```nushell "foo" | print ``` works again # Tests + Formatting - 🟢 `toolkit fmt` - 🟢 `toolkit clippy` - ⚫ `toolkit test` - ⚫ `toolkit test stdlib` # After Submitting --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| nu_plugin_custom_values | ||
| nu_plugin_example | ||
| nu_plugin_formats | ||
| nu_plugin_gstat | ||
| nu_plugin_inc | ||
| nu_plugin_python | ||
| nu_plugin_query | ||
| nu-cli | ||
| nu-cmd-base | ||
| nu-cmd-dataframe | ||
| nu-cmd-extra | ||
| nu-cmd-lang | ||
| nu-color-config | ||
| nu-command | ||
| nu-engine | ||
| nu-explore | ||
| nu-glob | ||
| nu-json | ||
| nu-parser | ||
| nu-path | ||
| nu-plugin | ||
| nu-pretty-hex | ||
| nu-protocol | ||
| nu-std | ||
| nu-system | ||
| nu-table | ||
| nu-term-grid | ||
| nu-test-support | ||
| nu-utils | ||
| 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.