Skip to content
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

Revert "Changed continuation_indent_size to 4" #134

Merged
merged 1 commit into from
Jan 3, 2018

Conversation

bradmcmanus
Copy link
Contributor

This reverts commit ed26117.

As per discussion from the GitHub issue [1], the default continuation
indent for Android should be 8 rather than 4. This matches the Android
Kotlin style guide.

[1] #120

This reverts commit ed26117.

As per discussion from the GitHub issue [1], the default continuation
indent for Android should be 8 rather than 4. This matches the Android
Kotlin style guide.

[1] pinterest#120
@shyiko
Copy link
Collaborator

shyiko commented Jan 3, 2018

@bradmcmanus 🙇‍♂️

@shyiko shyiko merged commit c70c5ad into pinterest:master Jan 3, 2018
@bradmcmanus
Copy link
Contributor Author

hey @shyiko -- I notice that this commit is mysteriously not present on new releases of ktlint (I would expect it to be present on all releases after 0.14). did you accidentally force push this commit out? or maybe you removed it on purpose? thanks!

@shyiko
Copy link
Collaborator

shyiko commented Feb 27, 2018

Hi @bradmcmanus.
I keep forgetting to ask clarification on android/kotlin-guides#37 but it looks like continuation_indent_size=4 might become official (for example, android/android-ktx is using ktlint --android profile) and so I have reverted the change to avoid "back and forth" between 4 and 8.

@bradmcmanus
Copy link
Contributor Author

@shyiko thank you for the clarification. I agree that the back and forth is troublesome. 4 is reasonable, especially if ktx is using 4. 4 it is!

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