You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 230b034
Browse filesBrowse the repository at this point in the historyBrowse files
Detect a group export from the child selection metadata, not the group prefix
Ticking a populated group row stores that group's loaded children stamped with
isSelectedViaGroup, not the group key itself. beginExportWithTemplate looked only for
the group prefix, so the card-group case this PR enables took the non-group path: it
sent the loaded transaction IDs and no cardID: filter, exporting incompletely whenever
a group's children were paginated.
Both export paths now share getGroupExportScope so the two detections can't drift
again, and the test fixture stores the child-only shape the provider actually writes,
which reproduces the failure.
Co-authored-by: Yauheni Horbach <ZhenjaHorbach@users.noreply.github.com>
// The export templates available to the user, pre-grouped and sorted alphabetically. The basic export is part of the default group so it's sorted alongside
@@ -1964,7 +1981,7 @@ function useSearchBulkActions({queryJSON}: UseSearchBulkActionsParams) {
1964
1981
// which most templates can't be scoped by, so template exports are hidden for it. Reconciliation - All Expenses is
1965
1982
// the exception on a card-grouped search (Card statements and Card accruals): the selected card groups become a
1966
1983
// `cardID:` filter, which is exactly the card-spend scope that template reports on.
0 commit comments