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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update: treat all literals like boolean literal in no-constant-condition #13245
Update: treat all literals like boolean literal in no-constant-condition #13245
Changes from 7 commits
3afc750
96d0834
540bb20
6eb51a8
17787ea
b0c2e70
c4c8426
ce019be
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#11308 did not handle following code:
demo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is indeed a bug that should be fixed whether or not #13238 gets accepted.
Could we maybe also this:
replace with just
inBooleanPosition
?I think it might fix similar bugs, such as:
Though, it seems that the whole condition starting with
node.operator === "||" &&
might be removed in this PR (if #13238 gets accepted), but we should also doublecheck what's happening with the recursion inisLogicalIdentity
. It already looks buggy in the actual version:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The cause is an inappropriate propagation of short circuit.
fixed in 96d0834