Fix to logic determining if context.matched in response #646
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.
Description:
Currently, if an API does not return the
context.matched
key in the search response thenItemSearch.matched
fails with aKeyError
. This is not ideal, because if for any reason appropriate information needed to determine the number of matched results is not present in the response, then according to the function's description, the function should returnNone
. This PR makes a minor fix to ameliorate the issue.P.S. I realize now that I've misspelled "Matched" as "Marched" in my branch name. Sorry.
PR Checklist: