refactor RowHeightSettings component to EUI layout#203606
Conversation
packages/kbn-unified-data-table/src/components/row_height_settings.tsx
Outdated
Show resolved
Hide resolved
30c3dee to
fbe834c
Compare
x-pack/plugins/lens/public/visualizations/datatable/components/toolbar.tsx
Outdated
Show resolved
Hide resolved
|
/ci |
1 similar comment
|
/ci |
cc2ecfb to
4b2c7e8
Compare
|
/ci |
c85d776 to
67c8bfc
Compare
|
/ci |
4 similar comments
|
/ci |
|
/ci |
|
/ci |
|
/ci |
src/platform/packages/shared/kbn-unified-data-table/src/hooks/use_row_height.ts
Show resolved
Hide resolved
|
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
79358d2 to
b3227ec
Compare
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
History
|
...cover-contextual-components/src/data_types/logs/components/summary_column/summary_column.tsx
Outdated
Show resolved
Hide resolved
...cover-contextual-components/src/data_types/logs/components/summary_column/summary_column.tsx
Outdated
Show resolved
Hide resolved
davismcphee
left a comment
There was a problem hiding this comment.
Code changes LGTM and it works as expected, thanks! It was a lot trickier than it probably should have been, but the good news is these changes will help simplify it for the next person 👍
|
Starting backport for target branches: 8.x https://github.com/elastic/kibana/actions/runs/13048127180 |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…208890) # Backport This will backport the following commits from `main` to `8.x`: - [refactor RowHeightSettings component to EUI layout (#203606)](#203606) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ania Kowalska","email":"63072419+akowalska622@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-30T08:12:02Z","message":"refactor RowHeightSettings component to EUI layout (#203606)","sha":"a376e9b16944c006975053295001690baec841bb","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","v9.0.0","release_note:feature","Team:DataDiscovery","backport:prev-minor"],"title":"refactor RowHeightSettings component to EUI layout","number":203606,"url":"https://github.com/elastic/kibana/pull/203606","mergeCommit":{"message":"refactor RowHeightSettings component to EUI layout (#203606)","sha":"a376e9b16944c006975053295001690baec841bb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203606","number":203606,"mergeCommit":{"message":"refactor RowHeightSettings component to EUI layout (#203606)","sha":"a376e9b16944c006975053295001690baec841bb"}}]}] BACKPORT-->
Summary
Closes: [OneDiscover][UnifiedDataTable] Change RowHeightSettings design to align with EUI #203378
PR focuses on adjusting current RowHeightSettings view to EUI layout.

Current view:
EUI view:

Changes:
2.1) Switching between "Auto" and "Custom" options should persevere input value (but shouldn't influence row count if in "Auto" mode)
2.2) While in "Auto" mode, number input should be disabled (but it shouldn't be hidden, like slider in current version)
2.3) Switching back from "Auto" to "Custom" view, the number input value should be applied as row count
Keeping input state separate from row height settings, but in sync while
custommode is on, required some wider changes, both in Discover and Visualization. I also unified map of values forsingleandauto.Previously Discover used
-1forautoand0for single, Visualization usedundefinedforautoand1forsingle.Currently it's unified to
-1forautoand1forsingle. Please see table below.auto-1undefined-1single011Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelines