-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
running ALEFix on save #591
Comments
You can't accomplish this with a simple The jobs for fixing files run asynchronously, so |
I'll have to make a note to change |
This is supported with an option now. See |
wow, thank you for the incredibly quick turnaround! |
Not sure if this can be fixed but when I do a :wq in NeoVim I get these errors:
|
Please open a new issue with steps for repeating the bug. |
Hello! I am a new user of ale, I noticed the work done on #571, and have started trying to use it. I'm running into issues when trying to run it on save (which is being tackled by #570), but figured I might as well ask in case it is due to user error.
Here are my configs:
I'm noticing a few things:
a. vim complains that the buffer has not yet been saved when trying to quit
b. if i very quickly quit before the buffer updates with the change, the fix won't actually occur (e.g, via
:wq
.Is this due to some async feature of ale? I previously used neoformat to do something similar, for which this doesn't occur.
when specifying ale_fixers for javascript, if I change the order of eslint and prettier so that eslint comes before prettier, the
javascript_prettier_options
don't get applied.If I don't specify
ale_javascript_prettier_options
,ALEFix
runs into an errorThank you for doing such amazing work!
The text was updated successfully, but these errors were encountered: