You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be amazing if the parse error, or the documentation that the error directs the user to, actually specifies what a valid field looks like.
The following error message is not informative:
Could not parse '/home/user/project/stack.yaml':
Aeson exception:
Error in $.compiler: failed to parse field 'compiler': Invalid wanted compiler: 8.8.0-20190613
See http://docs.haskellstack.org/en/stable/yaml_configuration/
The description below from the documentation does not provide enough information for the user to understand what is a valid compiler field.
This uses the same syntax as compiler resolvers like ghc-7.10.2 or ghcjs-0.1.0.20150924_ghc-7.10.2
BNF grammar, a regular expression, a plain language description would all be more useful for the user to diagnose the error.
What would be even better, since the list of known compilers is in scope for stack, as is the list of user defined compilers from the setup-info field, the error message should present something like this:
Could not parse '/home/user/project/stack.yaml':
Aeson exception:
Error in $.compiler: failed to parse field 'compiler': Invalid wanted compiler: 8.8.0-20190613
Perhaps you wanted of one:
[known-ghc]: ghc-8.0.2
[known-ghc]: ghc-8.2.2
[known-ghc]: ghc-8.4.4
[known-ghc]: ghc-8.6.5
[setup-info]: ghc-8.8.0.20190613
Does not support the following valid compiler value:
Steps to reproduce
Run:
with this
stack.yaml
:Expected
Try to build with the alpha version of GHC 8.8
Actual
Fails to parse with an error message that does not provide the user with the requisite information to correct the issue at hand.
Stack version
Method of installation
Don't remember. It was like 3 years and a half dozen upgrades ago.
The text was updated successfully, but these errors were encountered: