fix(linter): do not glob for invalid eslint config filenames in plugin #26409
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.
Current Behavior
The
@nx/eslint/plugin
globs for.eslintrc.base.json
andeslint.base.config.js
workspace root files, which are not valid ESLint config filenames. The ESLint CLI wouldn't pick them up directly, and we shouldn't infer or process them. They are only used as part of a valid config file name that extends from them.Expected Behavior
The
@nx/eslint/plugin
only globs for valid ESLint config filenames.Related Issue(s)
Fixes #26388