-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Mango match_failures/2 function
#6080
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
Open
jcoglan
wants to merge
16
commits into
main
Choose a base branch
from
mango-match-failures
base: main
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.
+1,461
−114
Open
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
49e4865
fix: The match/2 rule for filtering out <<>> should filter []
jcoglan 6a5088e
fix: Normalize negations inside $allMatch and other operators
jcoglan 28bed98
feat: Make mango_selector:match/2 return a list of failures
jcoglan 2d38eab
chore: Replace `Cmp` argument to `mango_selector:match/3` with a record
jcoglan 592eb95
feat: Record the paths where selectors fail to match
jcoglan ef17535
feat: "verbose" mode for `mango_selector:match/3`
jcoglan 40c4ab8
feat: Return VDU failure reports to the caller
jcoglan e2bfdc2
chore: Add some benchmarks for Mango selector matching
jcoglan 85728f8
fix: Mango VDUs should omit the `oldDoc` field from the matching stru…
jcoglan 846f89f
docs: More detailed explanation of the behaviour of the oldDocs field…
jcoglan 53cc327
fix: Raise an error if a Mango VDU contains invalid top-level fields
jcoglan d09c7e3
feat: Validate JS and Mango `validate_doc_update` on PUT /db/_design/doc
jcoglan b657e8b
fix: Selectors like {"$not":{"$allMatch":S}} (and "$elemMatch" and "$…
jcoglan e072153
fix: Format Mango VDU errors correctly when a doc contains an empty-s…
jcoglan f10bf98
fix: Do not split literal field names like "a.b" into separate path e…
jcoglan 384cd8e
fix: Reject Mango VDUs if they contain invalid field names or invalid…
jcoglan 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
Oops, something went wrong.
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.
Wonder if this will catch all possible mango_error errors. What about
{mango_error, mango_selector, {bad_arg, ...}}. Maybe we can just doSo we don't have to worry about every single corner case here
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.
This results in responses containing literal Erlang values, which I'd rather avoid. I'm not sure how else to write a generic error formatting block that does not have this problem.
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.
We do have a function to format those in a dedicated module, that might work
{_Code, _Name, Msg} = mango_error:info(Mod, Reason), {reply, {error, {compilation_error, Msg}}, St}Even if we didn't it might still be preferable to return some ugly error which makes sense rather than a 500 crash which doesn't