Mats Stijlaart
Mats Stijlaart
I see your point, but in my honest opinion, I think the author of the article has another alternative. Besides the two options he presents (`import Models` and `import Models...
I've made this check less strict in the new version of elm-analyse (0.13.0). ``` import Foo exposing (..) // Still a violation import Foo exposing (Bar(..)) // Not a violation...
Yes this is an option and yes, I thought about this as well. So in my opinion the pros for this are (if there are more please let me know):...
I'm planning to do some research on this topic to come up with a great solution. Will ping you all when I get some ideas/plans.
Thanks @jhf for your PR. If I understand correctly you are currently running `elm-analyse --format=json`, but the output of the process is not correct JSON. For the simplicity of the...
If you can update the PR, that would be really cool. I do not have much time on my hands at this moment for this project :(.
@andys8. Good point. I'll add a ticket for it.
DuplicateImpots are fixed in elm-format (0.7.0). Please use that instead of elm-analyse to fix duplicate imports.
Yes. This was originally designed how elm test functioned in `0.18`. It would make more sense to include test files as well at this moment
A change has to be made to make this work. I propose to extend the mechanism of collecting source files to also collect the test files. This would only apply...