Fix: Removing curly quotes in no-eq-null report message #9852
+6
−4
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.
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
Default, but doesn't matter
Please show your full configuration:
What did you do? Please include the actual source code causing the issue.
What did you expect to happen?
Error message: Use == when comparing to null.
What actually happened? Please include the actual, raw output from ESLint.
Got an error message, but it uses a multibyte character that does not render well in some contexts and furthermore is inconsistent with the rest of the core rules.
What changes did you make? (Give an overview)
Changed the lint message for no-eq-null to avoid using multibyte characters (curly quotes).
Is there anything you'd like reviewers to focus on?
Does this feel consistent with messages in other core rules?