-
Notifications
You must be signed in to change notification settings - Fork 372
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
Support JSONPath
in error messages
#1807
Open
Gabriella439
wants to merge
2
commits into
yesodweb:master
Choose a base branch
from
MercuryTechnologies:gabriella/jsonpath
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
name: yesod-core | ||
version: 1.6.24.2 | ||
version: 1.6.25 | ||
license: MIT | ||
license-file: LICENSE | ||
author: Michael Snoyman <[email protected]> | ||
|
@@ -26,7 +26,7 @@ library | |
hs-source-dirs: src | ||
|
||
build-depends: base >= 4.10 && < 5 | ||
, aeson >= 1.0 | ||
, aeson >= 2.1.0.0 | ||
, auto-update | ||
, blaze-html >= 0.5 | ||
, blaze-markup >= 0.7.1 | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the symmetry with the
parseInsecureJsonBody
, but I must admit I'm curious about this implementation.It seems like we have a two step process here - first piping the
ConduitT _ ByteString _ ()
into a JSON parser to get an intermediateValue
, and then callingifromJSON
on that value.But
eitherDecodeStrict
works on lazy ByteString, and callsifromJSON
too:If we did
rawRequestBody .| sinkLazy
, then we'd get aLazy.ByteString
, which we could provide toeitherDecodeStrict
and that would give us the JSON path error, albeit pre-formatted in theString
error message. But that's what we end up doing anyway, so it may not be too bad.But I'm also hesitant to change the implementation of a core bit of this without understanding why it is the way it is.
@snoyberg do you have any thouughts on this? tl;dr: this implementation requires an
aeson >= 2.1
bound, and theeitherDecodeStrict
implementation would work for our current bounds.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think adding a strict lower requiring
aeson
2 of any kind may be a problem, I know of at least a few companies out there that haven't been able to migrate over yet. Would it be possible to keep backwards compat with CPP?