-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Use SearchResult component #14867
Use SearchResult component #14867
Conversation
46824df
to
062940e
Compare
:name (if (or (= column :name) (nil? display_name)) name display_name) | ||
:matched_column column | ||
:matched_text match | ||
:context (when-not (#{:name :display_name :collection_name} column) match-context) ;; TODO pull this out somewhere more responsible |
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.
these "magic" column names should live in search.config
and both the when-not
and if
(L141) are a little jank, but I think the surrounding logic is going to change in the near future and don't want to waste cycles overoptimizing
5ad6b6c
to
b7a6a77
Compare
Codecov Report
@@ Coverage Diff @@
## master #14867 +/- ##
==========================================
- Coverage 83.93% 83.92% -0.01%
==========================================
Files 389 389
Lines 30485 30504 +19
Branches 2171 2171
==========================================
+ Hits 25587 25600 +13
- Misses 2727 2733 +6
Partials 2171 2171
Continue to review full report at Codecov.
|
Update the backend to return much richer match data [Fixes #14832]
b7a6a77
to
0d06433
Compare
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.
Looks like a few things are missing before this can go in and we can test further.
- We should use SearchResult on both the full search results page and in type ahead results.
- The
Our analytics
collection isn't showing up as the collection when something is saved there. I think that's due to the back end treating that collection strangely. - I think Metrics and Segments might not be accounted for yet which also tells me we need to improve our fallback case.
d4f23e7
to
4c8d878
Compare
4c8d878
to
49584f2
Compare
49584f2
to
5625858
Compare
...and update the backend to return much richer match data
[Fixes #14832]