mirror of
https://github.com/nushell/nushell.git
synced 2025-05-07 08:22:58 +00:00
9f714e62cb
# Description Contributors to this projects will have a test failure if their `umask` is not set to `0022`. Apparently on Debian (at least on my install), it is set to `0002` which makes my test fail. While `0022` is safer than the value I have, I want to reduce the amount if issue new contributors could have. I am making this test not assuming anything and instead, reading the user umask. # Related discussion I see that the `umask` command implementation has been discussed in #12256 . We could use this and enforce a umask for tests who rely on this. I believe however (let me know what you think) that hard coded values are harder to read in the test. # User-Facing Changes N/A # Tests + Formatting All green on my side after this MR 👍 # After Submitting Documentation is not impacted --------- Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com>
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.