-
Notifications
You must be signed in to change notification settings - Fork 66
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
LG-4881: fix expanded rows with no sub-rows #2714
Conversation
🦋 Changeset detectedLatest commit: 84aa510 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 |
879b55a
to
84aa510
Compare
Size Change: -25 B (0%) Total Size: 1.39 MB
ℹ️ View Unchanged
|
@@ -35,7 +35,6 @@ const InternalRowWithRT = <T extends LGRowData>({ | |||
|
|||
const isExpandable = row.getCanExpand(); | |||
const depth = row.depth; | |||
const hasSubRows = row.subRows.length > 0; |
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.
This is intentional; check out this chat from another PR. When expanded content is open, the parent row should not be highlighted.
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.
It feels strange to me that there is a need to differentiate extended content from sub-rows here. Are there any deeper thoughts to that decision?
It was found as a regression when reviewing my PR upgrading to the latest LG and as it wasn't explicitly called out as a change in the packages/table/UPGRADE.md doc, I assumed this was a bug.
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.
Apologies for not adding it to the upgrade guide. I'll update it. It was missing from the initial implementation, and we caught it during the refactor.
Closing as this is working as designed 👍 |
✍️ Proposed changes
Merging this PR will:
isExpanded
unconditionally.🎟 Jira ticket: LG-4881
✅ Checklist
For bug fixes, new features & breaking changes
pnpm changeset
and documented my changesFor new components
🧪 How to test changes