-
Notifications
You must be signed in to change notification settings - Fork 459
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
[Feature] Support editorconfig #734
Comments
Partial dupe of #142, but each issue is unique enough to stand on its own. |
I would like to see this. My use case is using the official Android XML format, and should be easy to just export the editorconfig from IntelliJ and that Spotless read it to know how to sort the xml fields for example. |
That would be really convinient to have such thing in spotless. I would be great if you add this support for Maven and Gradle :) |
Need this for using .editorconfig for all file types (*.yml, *.sh, etc.) |
This would really solve a lot of headaches for our team's overall formatting style as we rely on .editorconfig. Would be nice to see an update coming supporting this. |
Need this feature to solve all the headache we've due to different formatting style used in |
+1 for this feature! |
Certainly, it's definitely a valuable feature! Initially, I even tried to configure Spotless to comply with the |
Any news on this long-awaited feature? |
Maybe you can give a try to:
|
Thus, official spotless support would be very, very welcome |
Any updates?👀 What do people use as a workaround currently? |
I’ve migrated code to Google Java and Android OS styling .. |
For Java code I only use prettier Java |
Support https://editorconfig.org
instead of this
you could simply do
which would simply figure out all the same information, and also presumably pass it to other things like
would inherit it.
possibly code or coordination of a general library for editor config in java here.
https://github.com/ec4j/editorconfig-gradle-plugin
The text was updated successfully, but these errors were encountered: