Use strict-equal instead of lossy-equal #526
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.
Overview
===
,!==
) instead of lossy-equal (==
,!=
)Testing
eslint-disable-next-line
Comment
Basically, I checked the type of variables and whether there is at least a primitive such as
"str"
,42
in comparison or not.I add null-check or undefined-check in some comparisons not to break.
Funny things: after adding rule 'eqeqeq':