Avoid unnecessary optional chaining in autofix for no-get rule when using useOptionalChaining option
#1286
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
…ptional when autofixing
this.get('foo.bar').baz // will error if either foo or bar is nullish "baz of undefined"
this.foo?.bar?.baz // (previous behavior) evaluates to `undefined`
this.foo.bar.baz // (updated behavior) errors with either "bar of undefined" or "baz of undefined"
This maintains the behavior more closely when a nested chain contains a nullish value.
raycohen
force-pushed
the
no-get-infer-non-optional-nesting
branch
from
1689e1d
to
4c2366c
Compare
bmish
changed the title
no-get rule when using useOptionalChaining option
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.
This maintains the behavior more closely when a nested chain contains a nullish value.