-
Notifications
You must be signed in to change notification settings - Fork 54
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
Autocomplete on non-q query params? - #509
Comments
Nullified by the change to include URIs in the q param. Discussed use cases for autocomplete on other params (especially user) but while we can see the potential, we don't want to go there yet. Other params are either not susceptible to autocomplete (e.g. date), limited in number of possibilities (e.g. motivation) or will be provided by the user or client (q and box) |
Should this be included in Search 3.0? (thumbs up/down on the comment please) |
I don't see convincing use case for autocomplete on |
Closing, won't fix |
Should there be a way to autocomplete on the URI index, rather than on the text index? I would expect not, but it seems asymmetric if query terms are not required (e.g. for semantic tag search).
The text was updated successfully, but these errors were encountered: