-
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
[Vis: Default editor] EUIficate date_ranges param editor #38647
Conversation
Pinging @elastic/kibana-app |
💚 Build Succeeded |
The behavior was not changed, also valid in previous versions: If I'm not wrong, the empty values request means any existing date. Maybe it is a great opportunity to think about placeholders for empty inputs - e.x. |
Yes please! Please work with whoever you need to to accomplish this. |
💚 Build Succeeded |
778abf6
to
81461a5
Compare
💚 Build Succeeded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, tested locally on Chrome, Mac.
💚 Build Succeeded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with one word change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with one suggestion but nothing important:
On narrow screens the config UI takes up the whole width which means there is enough space for the two date inputs to be shown beside each other (by adding the responsive prop: <EuiFlexGroup responsive={false} gutterSize="s" alignItems="center">
).
IMHO it looks better that way because the date ranges don't tend to get that long
vs
What do you think, @cchaos ?
@flash1293 good finding, thanks! 👍 Maybe you have an info of how many people using kibana on narrow screens? (I'm just curious, seems it is not really convenient on mobile devices) |
💔 Build Failed |
@sulemanof I don't :) Looking at dashboards is probably a common use case, editing visualizations not so much I would expect. I was more thinking about people having small browser windows because they show multiple kibana tabs at once |
retest |
Yes, good catch @flash1293 ! While we don't officially say that Visualize is mobile-friendly, we try to ensure the layout isn't completely broken. So I agree that it should add the |
💔 Build Failed |
retest |
💔 Build Failed |
💔 Build Failed |
406a4b3
to
629f5db
Compare
💚 Build Succeeded |
* EUIficate date_ranges param editor * Add unit tests * Move link before the list * Add validation * Fix comments # Conflicts: # src/legacy/ui/public/agg_types/controls/date_ranges.html
)" This reverts commit f39a027.
* EUIficate date_ranges param editor * Add unit tests * Move link before the list * Add validation * Fix comments # Conflicts: # src/legacy/ui/public/agg_types/controls/date_ranges.html
Summary
Part of #30922.
Fix #38867.
EUIfication of
date_ranges
control forDate Range
aggregation.The PR includes:
validate-date-math
anddocumentation-href
;validate-date-math
directive;DateRangesParamEditor
component, which includes validation tests (previously based invalidate-date-math
);Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.For maintainers