chore: configure eslint rules to show warnings instead of errors #995
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MaxKless
approved these changes
Feb 3, 2022
shauke
approved these changes
Feb 3, 2022
shauke
changed the title
shauke
changed the title
SGrueber
added a commit
that referenced
this pull request
May 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Type
[x] Other: ESLint configuration
What Is the Current Behavior?
Many eslint rules are configured to cause an error, which is sometimes disruptive.
What Is the New Behavior?
The eslint rules have been checked to cause only an error if it is necessary. All other rules only cause a warning.
Does this PR Introduce a Breaking Change?
[x] No
Other Information
AB#73844