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 no-exec-interpolated-command rule #46586
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
Uh oh!
There was an error while loading. Please reload this page.
[eslint-miner] eslint: add no-exec-interpolated-command rule #46586
Changes from all commits
85109b860b8f0c0bf4ff9File 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]
node.arguments[0]can be aSpreadElement(e.g.exec.exec(...args)), butgetDynamicCommandKindreceives aTSESTree.Nodeand passes it toisInterpolatedTemplateLiteral/isDynamicStringConcatenation— both will safely returnfalsefor aSpreadElement, so no crash. However the type annotationTSESTree.Nodeis misleading:CallExpression.argumentsis typed as(Expression | SpreadElement)[], sofirstArgcould be aSpreadElement. An explicit type guard keeps the intent clear and avoids a future TypeScript error if the parameter type is tightened.💡 Suggested fix
This makes the SpreadElement exclusion explicit and the remaining code can narrow
firstArgtoTSESTree.Expression.@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.