Uli-Z
Uli-Z
I’m not sure if this is a bug or an intentional limitation, but when I tick the “Save as default splitting options” checkbox, the choice is only stored in the...
## Background Discussion status and references: - PR #456 introduces “Paid By” + sorting; reviewers requested the format change in a separate PR. - Issue #455 asks for CSV↔JSON parity...
This PR introduces a lean, extensible import architecture and wires the Spliit‑JSON format as the first adapter. Goal: reliable import/export as a core capability to ensure data sovereignty and smooth...
## Summary - Fix #374: Every expense now distributes its full amount, even when minor units do not divide cleanly. Shares are computed with `decimal.js`, truncated toward zero to whole...
When you split an amount that can’t be divided cleanly to two-decimal precision (e.g. $1 ÷ 3), each share is rounded down ($0.33), so the shares add up to less...
### Description Currently, any member with access to a group can edit or delete any expense. If an expense is deleted, it disappears completely — there’s no way to see...
**Summary** This pull request addresses a critical data inconsistency bug that occurs when an expense is set to be split evenly, but a default (uneven) splitting configuration also exists. The...
See Issue #327 I corrected this behavior so that default splitting options are stored group-wide in the database. **Summary** - Introduced a new defaultSplittingOptions JSON column in the Group table...
See Issue #365 Updates expense-form.tsx so that Mark As Paid reimbursements always use the EVENLY split mode rather than the group’s saved defaults.
Previously, exporting groups with German umlauts in their names resulted in a 500 error due to incorrect handling of the header. This commit corrects the usage of the library to...