-
Notifications
You must be signed in to change notification settings - Fork 212
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
Add additional searching capabilities to orders api #138
Comments
In which ways does this issue differ from #137? (How do we distinguish filtering from searching?) We should probably merge the filtering and searching stuff into one issue to make sure all the fields we need can be filtered, right? This issue does not say anything about searching multiple fields at the same time, so that's out of the scope? |
As a user I would expect search to perform full text search on the entire record. This means if a user searched for "red blue black" any record that has any of those terms should be returned, and they should be sorted by number of search term hits. |
I see. When talking with Bret I thought we agreed that the SQL database is unsuited for full record searches. Something like Algolia or ElasticSearch comes to mind in that case. Also, why did you include |
Since we really aught to go down the generalized search provider route at some point, we are going to hold off on this end of things until we research that some more. For now, I can selectively add fields as needed to the API. Down the road @mraerino can help us add a search provider api for algolia or elastic serach. So... current status of this issue is that its on hold. |
- Do you want to request a feature or report a bug?
Feature
- What is the current behavior?
We can currently search orders by item and email
- What is the expected behavior?
To search all order fields:
The text was updated successfully, but these errors were encountered: