forked from extern/nushell
57ce6a7c66
Prior to this PR, `ls` would return `nothing` in an empty directory. After this PR, it returns an empty `List`. This makes the behaviour of `ls` more consistent and easier to reason about (IMO). This was prompted by a user noticing that `ls | where size == 0KB and type == file` breaks when run in an empty directory: ``` × Input type not supported. ╭─[entry #12:1:1] 1 │ ls | where size == 0KB and type == file · ─┬ ──┬── · │ ╰── only list, binary, raw data or range input data is supported · ╰── input type: nothing ╰──── ``` If people agree with this change, let's wait until after the 0.77 release so we have a bit more time to test it. |
||
|---|---|---|
| .. | ||
| 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-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-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.