mirrors/ruff
1
0
Fork 0
mirror of https://github.com/astral-sh/ruff.git synced 2025-08-04 02:38:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Improve the documentation of E201/E202 (#14983)

Browse source 
## Summary

The summary is misleading, as well as the
`whitespace-after-open-bracket` and `whitespace-before-close-bracket`
names - it's not only brackets, but also parentheses and braces. Align
the documentation with the actual behaviour.

Don't change the names, but align the documentation with the behaviour.

## Test Plan

No test (documentation).
This commit is contained in:
Dimitri Papadopoulos Orfanos 2024-12-15 16:20:04 +01:00 • committed by GitHub
parent 112e9d2d82
commit 2d15d7d1af
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
crates/ruff_linter/src/rules/pycodestyle/rules/logical_lines/extraneous_whitespace.rs
View file

@ -11,7 +11,7 @@ use crate::checkers::logical_lines::LogicalLinesContext;
use super::{LogicalLine, Whitespace};
/// ## What it does
/// Checks for the use of extraneous whitespace after "(".
/// Checks for the use of extraneous whitespace after "(", "[" or "{".
///
/// ## Why is this bad?
/// [PEP 8] recommends the omission of whitespace in the following cases:
@ -50,7 +50,7 @@ impl AlwaysFixableViolation for WhitespaceAfterOpenBracket {
}
/// ## What it does
/// Checks for the use of extraneous whitespace before ")".
/// Checks for the use of extraneous whitespace before ")", "]" or "}".
///
/// ## Why is this bad?
/// [PEP 8] recommends the omission of whitespace in the following cases: