This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
no-null-keyword: Allow strict comparison #2802
Merged
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
Allows `x === null`, but disallows `x == null`. The latter will be automatically fixed to `x == undefined`. [new-fixer] `no-null-keyword`: fix `x == null` to `x == undefined` [enhancement] `no-null-keyword` allows strict comparison Fixes: #2782
adidahiya
approved these changes
Jul 31, 2017
HyphnKnight
pushed a commit
to HyphnKnight/tslint
that referenced
this pull request
Apr 9, 2018
Allows `x === null`, but disallows `x == null`. The latter will be automatically fixed to `x == undefined`. [new-fixer] `no-null-keyword`: fix `x == null` to `x == undefined` [enhancement] `no-null-keyword` allows strict comparison Fixes: palantir#2782
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 checklist
Overview of change:
Allows
x === null, but disallowsx == null. The latter will be automatically fixed tox == undefined.Fixes: #2782
Is there anything you'd like reviewers to focus on?
CHANGELOG.md entry:
[new-fixer]
no-null-keyword: fixx == nulltox == undefined[enhancement]
no-null-keywordallows strict comparison