language-servers/ruff
1
0
Fork 0
mirror of https://github.com/astral-sh/ruff.git synced 2025-08-03 18:28:56 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Fix subscript comment placement with parenthesized value (#10496)

Browse source 
## Summary

This is a follow up on https://github.com/astral-sh/ruff/pull/10492 

I incorrectly assumed that `subscript.value.end()` always points past
the value. However, this isn't the case for parenthesized values where
the end "ends" before the parentheses.

## Test Plan

I added new tests for the parenthesized case.
This commit is contained in:
Micha Reiser 2024-03-20 21:30:22 +01:00 • committed by GitHub
parent fd3d272026
commit 9d705a4414
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 42 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

13
crates/ruff_python_formatter/src/comments/placement.rs
View file

@ -262,7 +262,9 @@ fn handle_enclosed_comment<'a>(
// 0
// ]
// ```
if comment.line_position().is_end_of_line() {
if comment.line_position().is_end_of_line()
&& expr_subscript.value.end() < comment.start()
{
// Ensure that there are no tokens between the open bracket and the comment.
let mut lexer = SimpleTokenizer::new(
locator.contents(),
@ -270,13 +272,14 @@ fn handle_enclosed_comment<'a>(
)
.skip_trivia();
// Skip the opening parenthesis.
let Some(paren) = lexer.next() else {
// Skip to after the opening parenthesis (may skip some closing parentheses of value)
if !lexer
.by_ref()
.any(|token| token.kind() == SimpleTokenKind::LBracket)
{
return CommentPlacement::Default(comment);
};
debug_assert_eq!(paren.kind(), SimpleTokenKind::LBracket);
// If there are no additional tokens between the open parenthesis and the comment, then
// it should be attached as a dangling comment on the brackets, rather than a leading
// comment on the first argument.