feat(lint): created local rule to use isNullish and nonNullish #2553
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.
Motivation
We would like to enforce the usage of functions
isNullish
andnonNullish
in the code whenever possible. As first step we look for instances of comparing a variable withundefined
and/ornull
.isNullish
Incorrect
Correct
nonNullish
Incorrect
Correct
Future Improvements
The rule will be improved to recognize nullish check even with the following cases (and their negation counterparty):
Note
In this PR, we will not solve all the new issues raised by the new rule, otherwise it would become too big: we add the exceptions to the rule with a
TODO
, for all the functions that we need to fix in other PRs.Changes
isNullish
usage.nonNullish
usage..find
function.TODO
associated.Tests
It raised issues, correctly, and we fixed it.