Inappropriate handling of elm.json for packages #112
Comments
|
Oh yes! good catch! thanks. |
bdukes
added a commit
to EngageSoftware/elm-dnn-http
that referenced
this issue
Jan 24, 2024
Until stoeffel/elm-verify-examples#112 is resolved
bdukes
added a commit
to EngageSoftware/elm-dnn-localization
that referenced
this issue
Jan 24, 2024
Until stoeffel/elm-verify-examples#112 is resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for the cool project. 馃尫
It seems that the latest v6.0.2 always requires "source-directories" property in
elm.json, butelm.jsonfor packages does not have "source-directories" property.Although it works if we set the "source-directories" property in
elm.jsonfor packages, it would be better behavior to check the "type" property and assume that the "source-directories" is./srcif the value is"package".The text was updated successfully, but these errors were encountered: