-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Meta: Custom time ranges per panel #17776
Comments
@snide or @cchaos - can I get some design help for this?
|
Playground PR: #39937 |
@stacey-gammon I can think in-depth on this next week (7/8) |
@stacey-gammon Here is a quick mock of a proposed design tweak to your solution. |
hmm, it looks great, but I want to run through some options to implement those changes, or maybe take a shortcut on some of the functionality to minimize the time needed to implement. In the ideal architecture, the embeddable panel wouldn't require knowledge about the customize panel time range action. This kind of separation would let us make per panel time range action an x-pack feature, as well as an example to other third party developers wanting to do something similar. Ideally, we'd keep all the logic about the per panel time range inside the per panel time range plugin (or I actually put it in a big "advanced embeddable actions" plugin). To do that we would have to expose a way for plugins to hook into this badge area. We could actually do this using our current Triggers and actions registry without needing to introduce a new registry, which is great. The problem is in the custom label. The customize panel time range needs to store that label data somewhere so it persists. This is essentially phase 2 of embeddables. Phase 2 of embeddables is a good amount of work and would push this from a 1 week to multi-week implementation time. If we can get away without the custom label, I think we can do this much faster. When phase 2 comes around we can always consider the label. What do you think? Coule we use an icon and a tooltip to get around the length? |
To summarize, you're just saying that in terms of the mocks, you want to hold off only on allowing the time range custom label input? Was there anything else that can't be done in this first phase? Ideally, you wouldn't want to hide the time-range under a tooltip. This would cause more motion by the user to find the time range and wouldn't work for static images (reports) or kiosk mode. |
Yep that's right @cchaos - i just want to avoid the custom label since it adds a lot of complexity. I've already implemented everything else (though you may want to pretty up the "badge" styling). Otherwise just blocked on allowing the superdatepicker to be disabled and pretty printing the date: |
In order to complete implementation of #3578, we need to complete the following steps:
In progress
Dave
EUI time range input controlIn progress
Nathan
Absolute/Relative/Now HOC time picker in Kibana, convert global time picker to use this new one.Done
Stacey
Improve embeddable communication layer - PRIn Progress
Stacey
Clean up time range handling with embeddables - PRStacey
Add time zone tests to ensure this PR doesn't break anything. Waiting on this PR to be merged first.In progress
Stacey
Refactor panel code in prep for pluggable panel actionsMock:
cc @nreese @snide
The text was updated successfully, but these errors were encountered: