Hook up saved search APIs. #1368
Merged
Conversation
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 hooks up the placeholder locations in the Navigator UI with the saved search APIs. When a user is logged in, we add a "Save Results" button to the search results page, and pressing that button will fire an API request to save the current search filters and query to the database. This involved pulling out the pieces of the search state object that Algolia's InstantSearch API manages into the format our API accepts. On the main dashboard page, we perform the reverse operation, querying our API for saved searches, and then reconstituting a simulacrum of the serach state object, solely for the purposes of generating the URL query parameters directly from that object, which is how the search results page normally works.
richardxia
requested review from
jjfreund,
schroerbrian,
lgarofalo and
katerina-kossler
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This hooks up the placeholder locations in the Navigator UI with the saved search APIs.
When a user is logged in, we add a "Save Results" button to the search results page, and pressing that button will fire an API request to save the current search filters and query to the database. This involved pulling out the pieces of the search state object that Algolia's InstantSearch API manages into the format our API accepts.
On the main dashboard page, we perform the reverse operation, querying our API for saved searches, and then reconstituting a simulacrum of the serach state object, solely for the purposes of generating the URL query parameters directly from that object, which is how the search results page normally works.
Since I made some small UI changes, here's a screenshot showing what the "Save Results" button looks like: