-
Notifications
You must be signed in to change notification settings - Fork 78
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
Triple curly braces results in Exception: UnexpectedEvent {_received = Just (EventMappingStart Nothing), _expected = Nothing}
#129
Comments
Exception: UnexpectedEvent {_received = Just (EventMappingStart Nothing), _expected = Nothing}
Exception: UnexpectedEvent {_received = Just (EventMappingStart Nothing), _expected = Nothing}
You want the parser to special-case parse failure for something that isn't valid YAML? I think it would make more sense to handle this in a similar manner to how Pandoc 2.0+ handles the extended markdown variants with feature flagging and an extended parser. I'm not sure how well that would jive with the use of Personal/practical aside: I value this library as a simple and safe way to use That said I'm not the author or even a maintainer of this library, only a user. |
@chrissound you can get your desired behavior by using |
What we could do is deprecate |
I'm in favor of deprecating; I've known for a long time that it's a code smell to use |
Deprecation occurred in 0.8.29, closing. |
yaml 0.8.25
stack lts-10.0
I don't think my below example is valid Yaml, however I would think it would rather return
Nothing
rather than an exception.The text was updated successfully, but these errors were encountered: