-
Notifications
You must be signed in to change notification settings - Fork 67
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
Auto-configure when projects use Elm 0.19 vs 0.18 #141
Comments
I've spent the last 2-3 hours trying to get elm-mode working with my 0.19 project properly, but haven't been successful. Here's what I tried:
Nothing worked. My brain is fried. Any help would be appreciated. |
Please can you be more specific than "nothing worked"? What steps did you follow, what did you expect, and what happened instead? |
Should we expect |
Yes, correct. See #142 for the completion-specific side of things. It's not pretty. |
I don't know if you get this often or not, but I just wanted to thank you for your hard work and dedication for working on this project. The whole |
Thanks, I appreciate it, but I should also caution that I haven't concretely tackled it yet. :-) It was frustrating to get |
Nevertheless, it is a noble effort. I don't have much in the way of finances to remunerate you for your hard work, but I figured a word of encouragement wouldn't hurt. :-) |
The 0.19 config is now the default. I no longer plan to pursue auto-configuration for older Elm versions. |
As detailed in #138 (comment), it's now largely possible to configure
elm-mode
for Elm 0.19 projects, but it would probably be better if this were auto-detected. In fact, the presence ofelm.json
vselm-package.json
should be enough of a clue in most cases.(Noting this here for future implementation by myself or another contributor.)
The text was updated successfully, but these errors were encountered: