-
Notifications
You must be signed in to change notification settings - Fork 80
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
fix(datagrid): propagate cell rendering changes only to owned rows #1489
Conversation
Thank you, 🤖 Clarity Release Bot |
This change prevents propagation of cell rendering changes to rows owned by nested datagrids.
fa7cc73
to
3654707
Compare
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
@kevinbuhmann can you add, here or in a separeate PR, a demo page and/or storybook example for nested datagrids (in details and expanded rows) to be easily visually tested. A lot of people are using those patterns.
We have a datagrid nested in a datagrid detail in the stories. A datagrid nested in an expandable row is not a valid pattern for accessibility reasons. |
This comment was marked as outdated.
This comment was marked as outdated.
Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary. |
This change prevents propagation of cell rendering changes to rows owned by nested datagrids.
CDE-2199
closes #1485
PR Checklist
PR Type
Bugfix
What is the current behavior?
If the detail pane of a datagrid contains another datagrid with less columns than the outer datagrid, closing the detail pane results in the error:
row.cells.get(...) is undefined
.Issue Number: #1485, CDE-2199
What is the new behavior?
No error is thrown, and the correct cells are hidden.
Does this PR introduce a breaking change?
No.