Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes: #5878
The simplest fix is just make
error_make
always returnsResult::Err
.Breaking changes
I found that
error_make
is supporting pipeline input, which makes harder to adjust$env.LAST_STATUS_CODE
to1
, to achieve this, we need to consider output result fromtable
command, or make changes ineval_block
.More importantly, it's hard to make a decision if we get the following output value:
Value::Error(..)
[Value::Int(..), Value::Error(..), Value::Int(..)]
[Value::Error(..), Value::Error(..)]
Should
nu
think the result is success or not?So I remove pipeline input support for
error_make
, and makeerror_struct
fromoptional
torequired
.Tests
Make sure you've done the following:
Make sure you've run and fixed any issues with these commands:
cargo fmt --all -- --check
to check standard code formatting (cargo fmt --all
applies these changes)cargo clippy --workspace --features=extra -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect
to check that you're using the standard code stylecargo test --workspace --features=extra
to check that all the tests pass