-
Notifications
You must be signed in to change notification settings - Fork 145
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
atom-elm-format guideline changes #225
Conversation
Since 2.0 the default is to format on save 🎉
Great, thanks for the update! |
@benjick I actually just reverted this.... having format-on-save be the default is the existing checkmark in the "Format on Save" column. The warning in the "Formatting" column is because is because of this (#104):
The behavior when I tested it was that if format-on-save is turned off and the file is not saved before running the manual formatting command, then there are some problems. |
Oh okay, now I understand. Sorry about that. I will look into making it Which is preferred? Saving the file or just replacing the buffer? On 31 Aug 2016 19:33, "Ɛərɪn VonderHaar" notifications@github.com wrote:
|
Okay I read the guidelines now, will look into this! |
@benjick I assumed different things might be conventional for different editors, so didn't want to dictate that. Maybe check out popular atom formatting plugins for other languages and see what's common? |
The thing I do now I borrowed from eslint, but I think it's more important On 31 Aug 2016 20:48, "Ɛərɪn VonderHaar" notifications@github.com wrote:
|
atom-elm-format guideline changes
Since 2.0 the default is to format on save 🎉