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.
[eslint-miner] eslint: add require-return-after-core-setfailed rule #44697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[eslint-miner] eslint: add require-return-after-core-setfailed rule #44697
Changes from all commits
0fcba1d86a8b1cFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] The test suite is missing coverage for
core.setFailed()inside aswitchcase body — the rule explicitly handlesSwitchCasenodes, but there's no test exercising that path.💡 Add a switch-case invalid test
And a valid counterpart:
`switch(x) { case 'a': core.setFailed('bad'); break; }`Without this, the
SwitchCasevisitor in the implementation is untested.@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/codebase-design] Top-level
ExpressionStatementbodies (module-levelcore.setFailed()followed by more statements) won't be caught — the rule only walksBlockStatementandSwitchCase, missing theProgrambody.💡 Add a Program visitor
In CommonJS scripts, top-level code is common. Without this, a module-level
core.setFailed()followed by more code won't be flagged.@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.