Change operator-linebreak to before instead of after. #24
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.
I am proposing that we change our operator line break to either
before
or just turning it off completely.Current (after):
This PR (before):
I particularly like
before
much better with conditionals and terns:As I said before, I would also be okay with removing any before or after rule entirely. I mostly just hate being forced to use after, especially when conditionals and terns are longer and I am using split pane views with more "real life" code examples:
😢 (Sam with after)
In this paritcular case, the
? : || &&
characters can get cut off in the current pane, forcing me to horizontally scroll to see what is going on😄 (Sam with before)
With before, the operators are always visible and aligned with each other.