-
Notifications
You must be signed in to change notification settings - Fork 1
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
ResultTable: HeaderCell and Cell rendering tweaks #210
Conversation
- Do not wrap `HeaderCell` children in a `span` by default because it makes providing a custom `HeaderCell` harder. - Support `headerCellProps` and `cellProps` to accomodate the very common pattern of needing to only pass props to the header/cell components.
🦋 Changeset detectedLatest commit: 6d0e89a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
}, | ||
j | ||
) => ( | ||
<HeaderCell key={j} colSpan={colspan} {...headerCellProps}> | ||
<span> |
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.
Shouldn't this span be removed also here?
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.
Indeed. Thanks for catching this 👍
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.
There are quite a few things that I'm not in favor of regarding the structure of these components... and I suspect you feel similarly. However, this is an improvement, and one that we should make iteratively, instead of trying to do a huge lift. Thanks for your initiative on this @stellarhoof!
I'd like to get one more review & approval on this from @positiveVibes4all before merging.
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.
Looks good to go, this does not work with the current spark branch. I tested this on the draft PR in spark linked to this issue and it looked fine.
Coverage after merging cell-rendering-tweaks into main will be
Coverage Report
|
HeaderCell
children in aspan
by default because it makes overridingHeaderCell
harder.headerCellProps
andcellProps
to accomodate the very common pattern of needing to only pass props to the header/cell components.