-
Notifications
You must be signed in to change notification settings - Fork 642
feat: pivot table row grouping and subtotals #10269
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
feat: pivot table row grouping and subtotals #10269
Conversation
👷 Deploy request for peaceful-bassi-cbf284 pending review.Visit the deploys page to approve it
|
7b0b16e to
f3b0b3d
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.
I would appreciate if you rebase this PR after the updates 🙏 🙇
bc75347 to
f0245ad
Compare
499d787 to
ffd44f6
Compare
|
@ZeRego, thank you for your patience. Refactored per your recommendations and fixed some tests. Thanks again! |
|
Hi @agha4to 👋 I have been testing this and stumbled across a small bug: Screen.Recording.2024-07-12.at.16.40.35.mov |
|
Hi @almeidabbm, I've been thinking about Rows order and trying to implement something but I'm coming up against a few design questions. Currently in Pivots, even without this PR:
What's proposed:
Questions: In Configure chart, should Rows drags reflect in the Chart table only or also Results? A couple possibilities:
What about Metrics? Shouldn't those columns also be draggable to reorder the Chart columns? I think we need a design spec for all of this. There may be other loose ends to consider too. |
This comment was marked as resolved.
This comment was marked as resolved.
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.
Couple things causing build errors related to types, otherwise types look good
|
render link: https://lightdash-pr-11681.onrender.com |
|
I heard y'all were busy. I don't think there's a rush--no problem. Afaik, no remaining issues. Here's a look at the recent shading changes:
|
Co-authored-by: Irakli Janiashvili <[email protected]>
fix: avoid unsafely inferred `finalHeaderInfoForColumns: any`
18cb3c5 to
3f715c1
Compare
|
@agha4to approving code changes ✅ great work 🙌 |
# [0.1281.0](0.1280.0...0.1281.0) (2024-09-27) ### Features * pivot table row grouping and subtotals ([#10269](#10269)) ([25d4be8](25d4be8))
|
🎉 This PR is included in version 0.1281.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
* feat: pivot table row grouping and subtotals * refactor: move pivot subtotal data structure retrofit * test: pivot query result test fixes * refactor: remove use of any in pivot data structure * fix: table drilldown for metrics as rows, build issues * fix: use null marker for subtotals * fix: font settings, spacing, and group component wrapping * Update packages/frontend/src/hooks/pivotTable/pivotQueryResults.ts Co-authored-by: Irakli Janiashvili <[email protected]> * fix: whitespace * test: update pivot table data model tests * chore: avoid mutating code fix: avoid unsafely inferred `finalHeaderInfoForColumns: any` * fix: row number col misalignment and checkbox state * feat: pivot cell shading tweaks * style: fix LightTable whitespace --------- Co-authored-by: Tony Orciuoli <[email protected]> Co-authored-by: Irakli Janiashvili <[email protected]>
# [0.1281.0](lightdash/lightdash@0.1280.0...0.1281.0) (2024-09-27) ### Features * pivot table row grouping and subtotals ([lightdash#10269](lightdash#10269)) ([25d4be8](lightdash@25d4be8))
Closes: #10267
Description:
Adds row grouping and subtotal functionality to Pivot Tables. Pivot Table and non-Pivot Table components have distinct implementations, and ideally we'd like to combine them. This code does not do that. Instead, it keeps them separate. The underlying Pivot Table data structures have been "retrofitted" rather than rewritten at this time. I think that task is better done in the future when combining the two components, to avoid too much wasted effort.
Reviewer actions