Skip to content
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

Return richer API response for search #14832

Closed
tsmacdonald opened this issue Feb 15, 2021 · 0 comments · Fixed by #14867
Closed

Return richer API response for search #14832

tsmacdonald opened this issue Feb 15, 2021 · 0 comments · Fixed by #14867
Assignees
Milestone

Comments

@tsmacdonald
Copy link
Member

To support the SearchResult component

@tsmacdonald tsmacdonald self-assigned this Feb 15, 2021
@tsmacdonald tsmacdonald added this to the 0.39 milestone Feb 15, 2021
tsmacdonald added a commit that referenced this issue Feb 16, 2021
Still needs to add `context`

[Fixes #14832]

[ci skip]
tsmacdonald added a commit that referenced this issue Feb 17, 2021
Update the backend to return much richer match data

[Fixes #14832]
tsmacdonald added a commit that referenced this issue Feb 18, 2021
Update the backend to return much richer match data

[Fixes #14832]
tsmacdonald added a commit that referenced this issue Feb 19, 2021
Update the backend to return much richer match data

[Fixes #14832]
tsmacdonald added a commit that referenced this issue Feb 22, 2021
* Use SearchResult component

Update the backend to return much richer match data

[Fixes #14832]

* Increase the memoization cache for search scoring by common subseq (#14894)

* Increase the memoization cache for search scoring by common subseq

Also limit the size of input it can get

(Hopefully) [Fixes #14852]

* Don't group search results by type (#14898)

Respect the sorting done by the backend

* Format metrics and segments in search results; DRY up the code

* Add normalizedCollection(); show "Our Analytics" collection in search results

* Use SearchResult for typeahead results too
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant