Skip to content

fix: Continue to group nested keep-sorted blocks together if both group=yes and block=yes are set. #53

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 2 commits into from
Nov 20, 2024

Conversation

JeffFaer
Copy link
Collaborator

See git history of this PR to see how group.out has changed.

…up=yes and block=yes are set.

See git history of this PR to see how group.out has changed.
Copy link
Member

@KatrinaHoffert KatrinaHoffert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do low key wonder if the condition should be group or block rather than just doing this in group mode. Group mode is enabled by default, but perhaps it makes sense for nested keep-sorted blocks to still work if for whatever reason we only have block mode enabled. But eh, probably not worth the trouble of having to figure out if it is that simple and making other changes if it's not. This is a nice and minimal change.

@JeffFaer JeffFaer merged commit 6a58996 into main Nov 20, 2024
5 checks passed
@JeffFaer JeffFaer deleted the jfaer/fix_grouping_when_block branch November 20, 2024 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants