-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[pylint
] Better diagnostic range (PLR1702
)
#15578
base: main
Are you sure you want to change the base?
Conversation
|
code | total | + violation | - violation | + fix | - fix |
---|---|---|---|---|---|
PLR1702 | 220 | 102 | 118 | 0 | 0 |
It would be good to first discuss what the proper ranges are on the relevant issue (it's marked as needs design) |
(This was only supposed to be a draft, though.) Done. |
I'll put this back in draft until we aligned on a design on the issue. I'll reply there tomorrow |
That would be the correct decision. I just realized I had a off-by-one bug... (or is it?) This is not breaking though. The rule is in preview. |
Summary
Resolves #15570.
Test Plan
cargo nextest run
andcargo insta test
.