Open SahSantoshh opened 4 months ago
Yes, I agree! This should be a feature of Avo and have that search be done in-line. That's a better experience.
I don't think it should be super difficult to implement using turbo streams and replace the table results.
Would you be open to try and implement this feature? I could help with setting an approach and help you with navigating the codebase.
Sure, I would love to.
I'm laying down the approach for this refactor.
responseKind
should be turbo-stream
in order to be interpreted by Turbosearch_controller
, but at the BaseController#index
with the q
param populated with the value in the fieldBaseController#index
should see that and add it to the query using a new method we create around hereI believe this to be the "meat" of the feature. There are other things we need to consider but after we do these above.
Other considerations:
filters
, encoded_filters
, and othersThank you for taking this on! This is a feature we wanted to bring to our users a while back.
Hey @SahSantoshh, how does progress go with this? Can we help with anything?
It's been hectic days with quater-end. Planned to on it this weekend.
Awesome! LMK if I can help with anything. Thank you!
Feature
When a user enters a search query related to resources, the search results only appears in a dialog list upon clicking the search box. This can be limiting as users may not be aware of the hover functionality or might prefer to see all relevant resources listed directly.
Current workarounds
The search is shown in dialog and then we have to find the result from the dialog and navigate to the record details page.
Additional context