chore|style: ESLint errors and warnings === 0 #5450
Merged
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.
Resolves #5284, #5276, #5267, #5269
Impact: major
Type: chore|style
This PR:
eslint
warnings in our codebase, where applicableeslint
issues that would require a bit more refactoring / thought, such asreact/no-did-update-set-state
, which will be fixed when components are updated to be functional components.warning
overrides in ourpackage.json
file, which now means every eslint rule we follow is now an error.eslint-changed-files
CI step, which is no longer needed since every rule is an error, and our classiceslint
CI check takes care of all errors.Breaking changes
None for our codebase. Any custom code might need to be updated to obey the new lint rules.
Testing
eslint
warn
overrides foreslint
rules in our package.jsoneslint-changed-files
CI check run on this PR