-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support for Elm 0.19 #161
Comments
I'm wondering that too! I just ran into it. For the most part, everything just works. After updating my global versions of elm and elm-format, the few issues that I have come across are:
|
Did you have to create aliases for the old commands to map to the new commands (ex: |
Hmm, I did not do that. But the more that I think about it, my main usage
is just ale linting and formatting, both of which didn't need any changes.
…On Thu, Aug 23, 2018, 9:29 AM Brad ***@***.***> wrote:
Did you have to create aliases for the old commands to map to the new
commands (ex: elm-make -> elm make)? This might alleviate some of the
issues until everything is patched
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#161 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABva04nPbsSX8tNwHLHu7MW00qN8Deuvks5uTthUgaJpZM4WI1AL>
.
|
Cool thanks! I appreciate knowing this will work to some degree before putting in the effort integrating it into my configuration! |
It looks like json output format in elm 0.19 has been changed, here's example of new format being handled https://github.com/w0rp/ale/blob/master/ale_linters/elm/make.vim |
As 0.19 was just released, was wondering what steps I need to take to get this plugin working properly. Thanks in advance! 😄
The text was updated successfully, but these errors were encountered: