[flake8-bandit] Move unsafe-markup-use from RUF035 to S704#15957
[flake8-bandit] Move unsafe-markup-use from RUF035 to S704#15957MichaReiser merged 10 commits intoastral-sh:micha/ruff-0.10from
flake8-bandit] Move unsafe-markup-use from RUF035 to S704#15957Conversation
This comment was marked as resolved.
This comment was marked as resolved.
|
Thanks, this has to wait for the next minor release because it's breaking (selecting |
|
| code | total | + violation | - violation | + fix | - fix |
|---|---|---|---|---|---|
| S704 | 30 | 30 | 0 | 0 | 0 |
| RUF035 | 9 | 0 | 9 | 0 | 0 |
Clever, no :) But what I'd do is to lift the |
Switches to more verbose labels for references section.
44eec2b to
e4e1c58
Compare
|
Thanks @Daverball for rebasing |
…15957) ## Summary `RUF035` has been backported into bandit as `S704` in this [PR](PyCQA/bandit#1225) This moves the rule and its corresponding setting to the `flake8-bandit` category ## Test Plan `cargo nextest run` --------- Co-authored-by: Micha Reiser <micha@reiser.io>
…15957) ## Summary `RUF035` has been backported into bandit as `S704` in this [PR](PyCQA/bandit#1225) This moves the rule and its corresponding setting to the `flake8-bandit` category ## Test Plan `cargo nextest run` --------- Co-authored-by: Micha Reiser <micha@reiser.io>
Summary
RUF035has been backported into bandit asS704in this PRThis moves the rule and its corresponding setting to the
flake8-banditcategoryTest Plan
cargo nextest run