mirror of
https://github.com/nushell/nushell.git
synced 2024-11-24 01:13:37 +01:00
067ceedf79
# Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help) |
||
---|---|---|
.. | ||
build-all-maclin.sh | ||
build-all-windows.cmd | ||
build-all.nu | ||
build.rs | ||
coverage-local.nu | ||
coverage-local.sh | ||
install-all.ps1 | ||
install-all.sh | ||
README.md | ||
register-plugins.nu | ||
test_virtualenv.nu | ||
uninstall-all.sh |
run the scripts
Note
the following table must be read as follows:
- an
x
means it works- a
?
means no data available
.nu
scripts must be run asnu .../foo.nu
.sh
scripts must be run as./.../foo.sh
.ps1
scripts must be run aspowershell .../foo.ps1
let's say a script is called
foo
- an
x
in the./scripts
column meansfoo
can be run from./scripts
- an
x
in the root column meansfoo
can be run from the root ofnushell
- an
x
in the anywhere column meansfoo
can be run from anywhere!
script | ./scripts/ |
root | anywhere |
---|---|---|---|
build-all-maclin.sh |
x | x | x |
build-all-windows.cmd |
? | x | ? |
build-all.nu |
x | x | x |
coverage-local.nu |
x | x | x |
coverage-local.sh |
x | x | x |
install-all.ps1 |
? | x | ? |
install-all.sh |
x | x | x |
register-plugins.nu |
x | x | x |
uninstall-all.sh |
x | x | x |