-
-
Notifications
You must be signed in to change notification settings - Fork 722
chore(linter/no-unassigned-vars): move to category to correctness
#12832
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
chore(linter/no-unassigned-vars): move to category to correctness
#12832
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
lets see if this breaks anyone:
After fixing #12833, this rule has not had any false positives, and has raised correctness issues in user code. Making this rule have the "correctness" category feels like the right thing to do. |
CodSpeed Instrumentation Performance ReportMerging #12832 will not alter performanceComparing Summary
Footnotes |
3cf0d58 to
bf54c08
Compare
cf31e85 to
2c1dab6
Compare
bf54c08 to
a4e2cc1
Compare
Merge activity
|
a4e2cc1 to
f57335f
Compare
f57335f to
e6aea1b
Compare
e6aea1b to
c2d3464
Compare

No description provided.