Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An applicative
ObjectParser
letting us make "strict" object parsers. cc @hvrPerformance is slightly degraded, as you can suspect:
OTOH in case of missing / extra keys parser will fail early.
Motivation: for the TokenStream parser #560 such interface would be needed. The
objectField
could be a member of new class:BTW, why
parseJSON :: Value -> Parser a
and notparseJSON :: Parser a
, wherenewtype Parser a = Parser { runParser :: forall f r. JSONPath + -> Value -> Failure f r -> Success a f r -> f r }
(Probably because of manual instances, i.e. not using combinators like
withObject
)EDIT: if
aeson
is a wrong place for this, I'll add it toaeson-extra
.TODO: