Skip to content
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

Merged
merged 4 commits into from
Jul 24, 2024

Conversation

kevinbuhmann
Copy link
Member

This change prevents propagation of cell rendering changes to rows owned by nested datagrids.

CDE-2199
closes #1485

PR Checklist

  • Tests for the changes have been added (for bug fixes / features)
  • [N/A] Docs have been added / updated (for bug fixes / features)
  • [N/A] If applicable, have a visual design approval

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.

@kevinbuhmann kevinbuhmann requested a review from a team July 22, 2024 16:41
@kevinbuhmann kevinbuhmann self-assigned this Jul 22, 2024
Copy link
Contributor

github-actions bot commented Jul 22, 2024

👋 @kevinbuhmann,

  • 🙏 The Clarity team thanks you for opening a pull request
  • 🎉 The build for this PR has succeeded
  • 🔍 The PR is now ready for review
  • 🍿 In the meantime, view a preview of this PR
  • 🖐 You can always follow up here. If you're a VMware employee, you can also reach us on our internal Clarity Support space

Thank you,

🤖 Clarity Release Bot

This change prevents propagation of cell rendering changes to rows owned
by nested datagrids.
@kevinbuhmann kevinbuhmann force-pushed the kevin/nested-cell-rendering-fix branch from fa7cc73 to 3654707 Compare July 22, 2024 16:51
Copy link
Contributor

@valentin-mladenov valentin-mladenov left a 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.

@kevinbuhmann
Copy link
Member Author

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.

@kevinbuhmann kevinbuhmann merged commit 6c4b36e into main Jul 24, 2024
7 checks passed
@kevinbuhmann kevinbuhmann deleted the kevin/nested-cell-rendering-fix branch July 24, 2024 14:38
Copy link
Contributor

github-actions bot commented Aug 8, 2024

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.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Datagrid close detail issues error for nested datagrids: row.cells.get(...) is undefined
4 participants