Re-factor how the ESLint no-var
rule is enabled in the src/
folder
#12441
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.
This simplifies/consolidates the ESLint configuration slightly in the
src/
folder, and prevents the addition of any new files wherevar
is being used.[1]Hence we no longer need to manually add
/* eslint no-var: error */
in files, which is easy to forget, and can instead disable the rule in thesrc/core/
files wherevar
is still in use.[1] Obviously the
no-var
rule can, in the same way as every other rule, be disabled on a case-by-case basis where actually necessary.