Lint: add spaces after blocks #418
Merged
Conversation
This file contains 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
julesvirallinen
force-pushed
the
spacesAfterBlocks
branch
from
e6224a9
to
fd8560b
Compare
julesvirallinen
force-pushed
the
spacesAfterBlocks
branch
from
fd8560b
to
d84be2c
Compare
|
I agree, much easier to read 👍 |
oleeskild
approved these changes
Sep 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a very opiniated linter formatting rule, but hear me out.
Especially the publisher has a lot of very dense code. Extremely indendet oneliners after each other.
Reading this can be a huge mental load.
This linter rule auto-spaces out multiline code, which (at least for me) makes the code so much easier to parse.