Skip to content

[formatter] Stabilize fix for single-with-item formatting with trailing comment #16603

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

Merged
merged 1 commit into from
Mar 10, 2025

Conversation

MichaReiser
Copy link
Member

@MichaReiser MichaReiser commented Mar 10, 2025

Summary

This PR stabilizies the fix for #14001

We try to only make breaking formatting changes once a year. However,
the plan was to release this fix as part of Ruff 0.9 but I somehow missed it when promoting all other formatter changes.
I think it's worth making an exception here considering that this is a bug fix, it improves readability, and it should be rare
(very few files in a single project). Our version policy explicitly allows breaking formatter changes in any minor release and the idea of only making breaking formatter changes once a year is mainly to avoid multiple releases throughout the year that introduce large formatter changes

Closes #14001

Test Plan

Updated snapshot

@MichaReiser MichaReiser added formatter Related to the formatter breaking Breaking API change labels Mar 10, 2025
@MichaReiser MichaReiser marked this pull request as ready for review March 10, 2025 14:38
Copy link
Contributor

ruff-ecosystem results

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

@MichaReiser MichaReiser requested a review from ntBre March 10, 2025 14:49
@MichaReiser MichaReiser merged commit 41cd905 into micha/ruff-0.10 Mar 10, 2025
21 checks passed
@MichaReiser MichaReiser deleted the micha/stabilizie-with-items-bug-fix branch March 10, 2025 18:31
@MichaReiser MichaReiser mentioned this pull request Mar 10, 2025
2 tasks
MichaReiser added a commit that referenced this pull request Mar 13, 2025
…ng comment (#16603)

## Summary

This PR stabilizies the fix for
#14001

We try to only make breaking formatting changes once a year. However,
the plan was to release this fix as part of Ruff 0.9 but I somehow
missed it when promoting all other formatter changes.
I think it's worth making an exception here considering that this is a
bug fix, it improves readability, and it should be rare
(very few files in a single project). Our version policy explicitly
allows breaking formatter changes in any minor release and the idea of
only making breaking formatter changes once a year is mainly to avoid
multiple releases throughout the year that introduce large formatter
changes

Closes #14001

## Test Plan

Updated snapshot
MichaReiser added a commit that referenced this pull request Mar 13, 2025
…ng comment (#16603)

## Summary

This PR stabilizies the fix for
#14001

We try to only make breaking formatting changes once a year. However,
the plan was to release this fix as part of Ruff 0.9 but I somehow
missed it when promoting all other formatter changes.
I think it's worth making an exception here considering that this is a
bug fix, it improves readability, and it should be rare
(very few files in a single project). Our version policy explicitly
allows breaking formatter changes in any minor release and the idea of
only making breaking formatter changes once a year is mainly to avoid
multiple releases throughout the year that introduce large formatter
changes

Closes #14001

## Test Plan

Updated snapshot
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking API change formatter Related to the formatter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants