-
Notifications
You must be signed in to change notification settings - Fork 772
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
Track ktlint's code styles #82
Conversation
Continuation indent is now 2 instead of 4.
already in conflict 🙀 |
<option name="METHOD_ANNOTATION_WRAP" value="1" /> | ||
<option name="FIELD_ANNOTATION_WRAP" value="1" /> | ||
<option name="ENUM_CONSTANTS_WRAP" value="2" /> | ||
<indentOptions> | ||
<option name="INDENT_SIZE" value="2" /> | ||
<option name="CONTINUATION_INDENT_SIZE" value="4" /> | ||
<option name="CONTINUATION_INDENT_SIZE" value="2" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would have a big impact on many other codebases. We'd basically need to reformat all of them. What's the motivation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If your concern is only KtLint, then there's an open ticket to bring back the continuation indent: pinterest/ktlint#816
Change |
Retracted my 👎 . Chatted offline, and realized that we can put a tag on the current commit to give ourselves control over rolling this out across our code base. Bonus points if you go ahead and make that tag for us all. |
I’m gonna hold on this until we can roll forward with something that’s less invasive. |
Continuation indent is now 2 instead of 4.