-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Lens] Improve field dropdown readability #103701
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
I think we have two main options here:
My preference is to contribute this to EUI so that we can use this feature across Kibana, since it comes up frequently with long field names. |
We already use kibana/x-pack/plugins/lens/public/indexpattern_datasource/dimension_panel/field_select.tsx Line 209 in 5da47f8
|
during planning we decided to move forward with |
lets do the fix in Kibana for now and propose changes to EUI based on what we learn |
@mbondyra I agree that a |
@wylieconlon thanks for your comment, |
@MichaelMarcialis what do you think about that inconsistency? could we do this change just in the dropdown but not the selected value for the minor improvement it provides? Sounds like the alternative is wait for EUI which could be longer |
I'm personally fine with the notion of implementing the proposed partial/bandaid fix to give middle truncation to the dropdown options, even if it is temporarily inconsistent with the selected item truncation. It's an improvement on something that is potentially problematic at the moment, so that's a win in my book. As long we can easily change to the official EUI fix when that gets implemented in the future, I say go for it. |
Describe the feature:
When My field names are very long (a certain telemetry environment comes to mind)
I need To see the beginning AND the end of fields
So I can make a choice less painfully
Workaround today - you can hover over a field in the dropdown and get the browser-powered tooltip to see the full field name. There is no way to see what field the system is configured to use without first opening the dropdown and doing this hover and sometimes, if the index pattern is huge, the dropdown doesn't open to the position of the selected field until some data is returned from elasticsearch / kibana
Describe a specific use case for the feature:
Long field names that differ slightly in the last portion are difficult to read -
The text was updated successfully, but these errors were encountered: