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.

Sign up for GitHub

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

Jump to bottom

"Warning: stack-setup.yaml: Unrecognized field in SetupInfo: ghcjs" #1040

Closed
mgsloan opened this issue Sep 24, 2015 · 2 comments
Closed

"Warning: stack-setup.yaml: Unrecognized field in SetupInfo: ghcjs" #1040

mgsloan opened this issue Sep 24, 2015 · 2 comments
Assignees
@borsboom
Milestone
P1: Must

Comments

@mgsloan
Copy link
Contributor

mgsloan commented Sep 24, 2015

In #1030 I've added a field for ghcjs tarballs, which will cause this warning in versions of stack that lack the change. @snoyberg said it'd be fine to go ahead with changing stack-setup-2.yaml: commercialhaskell/stackage-content@9ef1c12

Since this format is designed to grow (hopefully without too many numeric versions), the FromJSON instance shouldn't warn about fields that are unrecognized.
@borsboom borsboom added this to the P1: Must milestone Sep 25, 2015
@borsboom
Copy link
Contributor

The same instances are used both to load stackage-content/stack-setup-2.yaml, and the setup-info field in local stack.yaml. We should show warnings for the latter, but hide them for the former. The code that loads the stackage-content/stack-setup-2.yaml can elect to not display the warnings for that case.

borsboom added a commit that referenced this issue Sep 25, 2015
@borsboom
Hide unrecognized field warnings for default stack-setup-2.yaml (#1040)
42bb3b3
@borsboom
Copy link
Contributor

Fixed in master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@borsboom borsboom

Labels
None yet
Projects
None yet
Milestone
P1: Must
Development

No branches or pull requests
2 participants
@mgsloan @borsboom