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.
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
feat!: Update shouldUseFlatConfig and CLI so flat config is default #17748
feat!: Update shouldUseFlatConfig and CLI so flat config is default #17748
Changes from 1 commit
d0dea8f
df69890
208d2bc
99e5f75
8ac03fa
728b4bc
7b359b0
4fc794c
bbf0119
8b30806
265105f
35ccf30
4816e25
File filter
Filter by extension
Conversations
Jump to
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.
After these changes,
npm test
will be logging more than 100 deprecation warnings until we drop eslintrc in v10.Can we avoid that?
allowFlatConfig = false
is passed only from tests, so we could update the condition inlib/cli.js
to avoid logging warnings while running tests:Then, we could update this test this way to make it work:
Or, perhaps even better, merge this test into the test for
ESLINT_USE_FLAT_CONFIG=false
as that's anyway the most realistic test:That would leave
npm test
with zero eslintrc deprecation warnings (assuming #17797 will be merged; those tests passallowFlatConfig = true
but mistakenly still work in eslintc mode, so they're mistakenly logging deprecation warnings).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.
Good suggestion, I went with the second approach.