[Emotion] Convert EuiDataGrid gridStyles to Emotion (Part 3)
#8006
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cee-chen
force-pushed
the
emotion/datagrid-1
branch
2 times, most recently
from
5d04264
to
f65e427
Compare
cee-chen
changed the title
gridStyles to Emotion (part 3)
cee-chen
force-pushed
the
emotion/datagrid-1
branch
2 times, most recently
from
6afaa83
to
d7d7e53
Compare
cee-chen
changed the title
gridStyles to Emotion (part 3)gridStyles to Emotion (Part 3)
- unfortunately can't be as specific here, has to be applied to top level datagrid styles
- handle this at topmost grid level, I personally don't think it makes any sense to split it up by component when they affect each other - more files makes it harder to write/predict + clean up several CSS unsets by assuming lack of borders rather than presence of borders
- some fontSize/lineHeight tweaking required to stay the same as prod (due to changes Caroline made to euiFontSize) + improve Emotion className labeling
- we can now obtain cell padding sizes from dynamic themes, hooray
- pass `gridStyles` down through the body and to the rows so CSS can be a bit flatter, as those styles only concern those components + convert enzyme tests to RTL
+ remove unnecessary show footer toggle - it's the entire point of the demo, why would we disable it? + remove flex in favor of EuiSpacer
- grid borders and header/footer underline/overlines were conflicting with one another - borders on header/footer cells were adding extra height to the cells themselves (unlike regular row cells)
…utils - VRT stories should use minimal data still for screenshot simplicity + add 2 new stories with more customizable controls, which lists the nested props documentation for each nested config
- allows us to expand props documentation & use controls for `rowHeightsOptions` + add test for lineHeight
cee-chen
force-pushed
the
emotion/datagrid-1
branch
from
d7d7e53
to
92e6fd8
Compare
mgadewoll
reviewed
Sep 6, 2024
packages/eui/src/components/datagrid/data_grid_styles.stories.tsx
Outdated
Show resolved
Hide resolved
+ remove `PRESERVED_FALSE_VALUE_PROPS` logic - we should let the defaultProps logic handle that instead and always show `false` props if they're non-defaults (testable on, e.g. `<EuiExpression uppercase={false} />`)
💚 Build Succeeded
History
|
mgadewoll
approved these changes
Sep 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Part of #6394
This PR looks intimidating in terms of file diff, but I promise the majority of it is just Storybooks! As such I strongly recommend following along by commit. The TL;DR of changes:
gridStyleto Emotion (rows, borders, and cell density)stories.utils.tsxfile as a way to generate fake 'components' that would fool Storybook's react docgen, as well as to share a stateful datagrid:QA
General checklist
- [ ] Checked in mobile- [ ] Checked for accessibility including keyboard-only and screenreader modes@defaultif default values are missing)- [ ] Checked Code Sandbox works for any docs examplesand cypress tests- [ ] If applicable, added the breaking change issue label (and filled out the breaking change checklist)