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

atom-elm-format guideline changes #225

Merged
merged 1 commit into from
Aug 31, 2016
Merged

atom-elm-format guideline changes #225

merged 1 commit into from
Aug 31, 2016

Conversation

benjick
Copy link
Contributor

@benjick benjick commented Aug 26, 2016

Since 2.0 the default is to format on save 🎉

Since 2.0 the default is to format on save 🎉
@avh4
Copy link
Owner

avh4 commented Aug 31, 2016

Great, thanks for the update!

@avh4 avh4 merged commit e551f2d into avh4:master Aug 31, 2016
@avh4
Copy link
Owner

avh4 commented Aug 31, 2016

@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):

When formatting a file, if the in-memory version of the file and the on-disk version of the file differ, then the plugin should format the in-memory version of the file. (Saving the file before formatting is also acceptable.)

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.

@benjick
Copy link
Contributor Author

benjick commented Aug 31, 2016

Oh okay, now I understand. Sorry about that. I will look into making it
compatible.

Which is preferred? Saving the file or just replacing the buffer?

On 31 Aug 2016 19:33, "Ɛərɪn VonderHaar" notifications@github.com wrote:

@benjick https://github.com/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:

When formatting a file, if the in-memory version of the file and the
on-disk version of the file differ, then the plugin should format the
in-memory version of the file. (Saving the file before formatting is also
acceptable.)

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.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#225 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAaTGGvNTc14ES4beyW41BNI7X2IF6tAks5qlbrMgaJpZM4Jt4to
.

@benjick
Copy link
Contributor Author

benjick commented Aug 31, 2016

Okay I read the guidelines now, will look into this!

@avh4
Copy link
Owner

avh4 commented Aug 31, 2016

@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?

@benjick
Copy link
Contributor Author

benjick commented Aug 31, 2016

The thing I do now I borrowed from eslint, but I think it's more important
to be compliant with the plug-in itself, than other plug-ins for the editor

On 31 Aug 2016 20:48, "Ɛərɪn VonderHaar" notifications@github.com wrote:

@benjick https://github.com/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?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#225 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAaTGI0uetrTgDDPhtXdKzgWG0jHQ2jjks5qlcs2gaJpZM4Jt4to
.

kutyel pushed a commit to kutyel/elm-format that referenced this pull request Apr 26, 2022
atom-elm-format guideline changes
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.

None yet

2 participants