-
-
Notifications
You must be signed in to change notification settings - Fork 960
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
update split transaction handling for csv export #2973
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger
Smaller No assets were smaller Unchanged No assets were unchanged |
demo build works as almost intended for newly split transactions, i.e. seems to count them correctly. but pre-existing splits in the demo-file seem to have a differing sort_order numbering structure? looking at the test data export, the splits range in value from 0 to -2, but in my actual data (and the newly created splits) have sort_orders ranging from -1 to -5 (or higher as appropriate) e: whoops and also have to handle some nulls |
okay, now works as intended, doesn't add extra 'null' to the line. my real data works as i wrote the new script, as does newly-created transactions. I'm guessing that the sort_order being 0 on some of the splits exported from the test-data is because of the test-data and not the performance of code under this PR. |
2cb1de5
to
d965232
Compare
628cc5d
to
35af118
Compare
Fixes #522
Current behavior: when exporting to CSV, any splits (child) transactions, Payee overridden by the parent transaction, and parent transactions are specifically ignored when exporting.
This PR changes the behavior so children have a "(SPLIT x OF y) " note prefixed to their
Notes
, parents have a "(SPLIT INTO X) " prefixed to theirNotes
, and Parents are included in the export. Splits are counted by using the inverse of the sort_order.There also seemed to be a typo. In my transactions table, it's "isChild" and "isParent" but existing logic appears to expect "is_parent". UPDATE: the "is_parent" logic is correct, but it shows as "isParent" in sqllitestudio.
Question: Do all split children have payees? I may have been a little too overzealous if not. Seems like yes though.
category: Bugfix
authors: [wdpk]
Fix exporting split transactions to CSV by including top-line transactions and noting the split.