-
Notifications
You must be signed in to change notification settings - Fork 34
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
[FEATURE] Sort Index Dropdown #293
Comments
I can pick up this issue. |
For this, please use ComboBox with |
@ashwin-pc -> would this be a good candidate to utilize the new |
@kgcreative yes, the new component should solve this issue. @frankschlehofer there is a new DataSources component thats exposed by the data plugin that should allow the user to use filter the datasource that they need from a long list. https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/src/plugins/data/public/data_sources/datasource_selector/datasource_selectable.tsx |
Hi @ashwin-pc, would the DataSources component replace the ComboBox entirely, or would it be used in addition to the ComboBox. I got the ComboBox without the DataSources working now, so I'm just a little unsure what the DataSources component would be doing exactly. Thanks! |
The current implementation is a combo box. @shanilpa is working on the future iteration of the datasource selector. He is the best person to ask this question to :) |
For now let's align on combo box as an incremental improvement. We can consider the data source component once the future iteration is a bit more defined |
Is your feature request related to a problem?
On domains with a large number of indexes, it may be difficult to find a specific index since the indices list is not sorted, simply displayed what is returned from the backend.
What solution would you like?
Sort the index array before displaying them. This should be a simple change here.
What alternatives have you considered?
Combing through large dropdown menus is the only other option, but is inconvenient for users.
Do you have any additional context?
The ML Playground has a similar fix implemented.
The text was updated successfully, but these errors were encountered: