-
Notifications
You must be signed in to change notification settings - Fork 211
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.
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
yaml-to-dhall --version
should not require SCHEMA argument
#1198
Comments
Gabriella439
added a commit
that referenced
this issue
Aug 3, 2019
Fixes #1198 This changes version to be a separate constructor for options parsing, in order to make invalid states unrepresentable and to fix issues like the above one.
Fix is up here: #1199 |
That was quick! 🤠 Thanks, @Gabriel439! |
@vvv: You're welcome! 🙂 |
mergify bot
pushed a commit
that referenced
this issue
Aug 6, 2019
* Fix `--version` flag handling for `dhall-json` package Fixes #1198 This changes version to be a separate constructor for options parsing, in order to make invalid states unrepresentable and to fix issues like the above one. * Undo `allowImports` changed This was a change I forgot to stash while working on the fix for the `--version` flag * Fix missing `Paths_dhall_json` in `dhall-json.cabal`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
yaml-to-dhall --version
should just work.Current behaviour:
The text was updated successfully, but these errors were encountered: