[Lens] Revisit flyout fields style from column to row compressed#120103
[Lens] Revisit flyout fields style from column to row compressed#120103dej611 merged 11 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors) |
I'd be OK with adding a supporting range slider to the number inputs assuming 1) there is enough space (i.e. using row compressed), 2) the related number inputs do not support an infinite range of numbers (i.e. they have a finite min and max), and 3) the changes made via the slide provide the user direct feedback via representation in visualization. I just want to make sure we're not relying on sliders alone for items that require precision, as the sliders aren't particularly good at that. |
Agree on all three conditions. In both
Will update the PR with the new components. |
|
Fixed the mobile layout for the flyout as proposed by @mbondyra : Replaced the Percentile numeric input with a range input: While the idea of replacing the
|
|
@elasticmachine merge upstream |
|
Tested on FF and it looks as expected. Approved! |
| {popoverOptions.length > 0 && ( | ||
| <EuiText textAlign="right"> | ||
| <EuiSpacer size="s" /> | ||
| {/* <EuiSpacer size="s" /> */} |
.../plugins/lens/public/editor_frame_service/editor_frame/config_panel/dimension_container.scss
Outdated
Show resolved
Hide resolved
MichaelMarcialis
left a comment
There was a problem hiding this comment.
Great work on this, @dej611. As mentioned in my comment below, I made a quick design PR for the flyout issue on smaller viewport sizes. Once that PR is merged into this branch, that will address my only concerns. Otherwise, this looks good to go. Approving now, assuming you'll be able to merge that design PR in without issue.
.../plugins/lens/public/editor_frame_service/editor_frame/config_panel/dimension_container.scss
Outdated
Show resolved
Hide resolved
* allow flyout to go full width on small viewports * remove hiding of layer panel when flyout open
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
…stic#120103) * 💄 Revisit form style + spacers * ✅ Fix tests * ✨ Replace percentile input with range * 💄 Fix mobile layout * 💄 Make searchbar go below flyout * 🔥 Remove unused jsx * [Lens] Refactor Flyout Design Updates (#14) * allow flyout to go full width on small viewports * remove hiding of layer panel when flyout open Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Michael Marcialis <michael@marcial.is>






Summary
Fixes #118391
Fixes #103778
Mostly changed field aspect from
columnCompressedtorowCompressedwith additional refactoring ofEuiSpacers, and Top Values Rank direction component.Updated test to match the new components.
Some questions
Top values > Number of valueshas both min and max defined. But other fields with min/max defined (i.e.Percentile) can apply as well.cc @MichaelMarcialis
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers