Compiler: elm make --warn --yes flags absent in 0.19

Created on 22 Aug 2018 · 4Comments · Source: elm/compiler

For elm 0.18, emacs was running elm-make --yes --warn --output=temp-file-output --report=json temp-file-source to read & fill out type annotations.
When I try to adapt these commands to elm 0.19, I notice flags --yes --warn are no longer accepted.

$ elm make --yes --warn --output=/dev/null --report=json $file
I do not recognize this flag:

    --yes

$ elm make --warn --output=/dev/null --report=json $file
I do not recognize this flag:

    --warn

Is there a replacement for this functionality or a better way to get type annotations?

Source

lmmarsano

👍1

Most helpful comment

Those flags did not get into 0.19. We will bring warnings back at some point in some form, but with the compiler rewrites, it was quite difficult and I did not want to block the release any longer.

For editor plugins that relied on flags for unintended uses, I do not have good recommendations. We would like to support things explicitly with actual APIs at some point, but we have not had support for that so far.

evancz on 22 Aug 2018

👍7

All 4 comments

Those flags did not get into 0.19. We will bring warnings back at some point in some form, but with the compiler rewrites, it was quite difficult and I did not want to block the release any longer.

evancz on 22 Aug 2018

👍7

What about the --yes flag , it missing just broke our CI?

flicaflow on 6 Sep 2018

👍1

What about using yes as an interim solution?

yes | elm make --output=temp_file_output --report=json temp-file-source

bruchmann on 6 Sep 2018

@bruchmann we're using vsts as our CI and putting yes | in front seems to cause that task to run indefinitely.

UPDATE: ... just ran it normally without the yes | and it downloaded packages and compiled fine on our CI... so a classic 'fixing a problem that we didn't have' scenario