fix: correct assignment operators#192
Merged
Sysix merged 2 commits intooxc-project:mainfrom Sep 16, 2025
Merged
Conversation
Member
|
How come there is no default lint rule to detect this 🤔 |
Contributor
Author
Maybe |
Member
|
Thank you, raised oxc-project/oxc#13796 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 PR fixes a bug where comparison operators (==) were mistakenly used instead of assignment operators (=) in the normalizeSeverityValue function.
This question seems strange, was it intended to be that way? 🤔