feat: add --max-consecutive-empty-lines setting - #165
Open
stigh wants to merge 8 commits into
Open
Conversation
stigh
force-pushed
the
max_consecutive_empty_lines
branch
from
February 20, 2026 22:17
e981942 to
62490ba
Compare
Collaborator
|
@stigh I can review this pr, if you intend to finalize it. This repo does have a working PR approval process again (it took a long time to get to that state, sorry). |
Contributor
Author
|
@pseewald, no problem! Glad to see some activity. I'll have a look soon. |
Contributor
Author
|
@pseewald, I'm now happy with this PR. Could you review? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #164.
This does not contain any tests, so is currently only intended as a proposal. This solves only one of the several limits with fprettify I need to solve to be able to define the code standard we use.
I can also add that I have a couple of other feature branches in the works at https://github.com/stigh/fprettify, which are cherry-picked into a development branch which hopefully will work towards the code standard we use.
If I get some kind of indication that this project has a working PR approval process, I intend to put in the extra effort to add the tests required, and the same with the other feature branches I have.