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

Use flycheck's new :default-directory option to handle projects with subdirs #10

Merged
merged 1 commit into from
Jul 11, 2016

Conversation

purcell
Copy link
Collaborator

@purcell purcell commented Jul 11, 2016

This enables the checker if and only if an existing elm-package.json can be found, and runs elm-make from the directory of that file.

The previous behaviour of allowing elm-make to implicitly create elm-package.json in the current directory - which could cause the checker initialisation to hang - is also therefore avoided. Initial invocation of elm-make is best carried out interactively, rather than implicitly.

Fixes #3, but is pending the next flycheck release: 0.29. This code works with the current MELPA snapshot package though, so you might consider committing this already, then not tagging a new stable version of flycheck-elm until the next flycheck stable release has been made.

…subdirs

This enables the checker if and only if an existing elm-package.json can
be found, and runs elm-make from the directory of that file.

The previous behaviour of allowing elm-make to implicitly create
elm-package.json in the current directory - which could cause the
checker initialisation to hang - is also therefore avoided.

Fixes bsermons#3.
@purcell purcell mentioned this pull request Jul 11, 2016
@bsermons
Copy link
Owner

Thanks for this! I had been watching that flycheck PR for a while so glad it finally landed. As long as it works with MELPA that is good enough for me.

@bsermons bsermons merged commit 30a6181 into bsermons:master Jul 11, 2016
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.

2 participants