-
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] Dimension editor should allow fieldless operations #75231
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
When we drop the requirement to remember the last used field, we could implement this with little effort by introducing a hidden virtual field All other interactions would continue in the same way, but it wouldn't switch back to the last used field e.g. when going from "Top values of field1" to "Filters" back to "Top values" - in this case you would have to pick a field again. @wylieconlon do you have another idea how we could represent this? |
I was expecting that we would implement the various pieces of this in three phases that can be done in parallel:
|
Makes sense, it seems like we need the first two things for a nice experience to merge the filters PR, then adding the third point as an improvement later (probably after 7.10) |
To support the filters aggregation and future calculations like math, we will need the editor to sometimes hide the field selector. When switching to and from the fieldless operation, Lens should remember the last-used field.
Introducing a fieldless operation should probably not affect any of the suggestion logic that we currently apply, such as auto-selecting a field for a function.
The text was updated successfully, but these errors were encountered: