Update search.json default fields to be more restrictive#10350
Merged
Conversation
Reduce default response load for search.json Patrons can still use `fields=*` to achieve the old results
for more information, see https://pre-commit.ci
mekarpeles
added
the
Priority: 1
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Reduce default response load for search.json
Patrons can still use
fields=*to achieve the old resultsRelated to #7673
Technical
Returns a
documentation_urlwhich ideally would return json but 🤷Testing
hit search.json and you should get less payload
Screenshot
Stakeholders