Decide Data Models for Zplit App.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Read the discussion on this issue, starting with the proposed payer-debtor-amount-total-currency structure and the offline data transfer idea. The issue does not identify code files, tests, or a settled model; first clarify the data model and synchronization requirements with maintainers. Done means the team has agreed on the model and its representation for transfer between devices.
Written by the indexing model from the issue text.
Description
This issue will track discussions related to finalizing the data models for the application. As this is a purely offline application, we will use a SQL Database offline to store all data. To transfer this data between devices, the currently ideated architecture will involve encoding any data to transferrable strings and then decoding on the receiving device.
One Data Structure proposed by Bruno is:
Payer-Debtor-Amount-Total-Currency-Description-Category-Location(optional)-Date and Time
Example for a $100 Transaction paid by X and split between X,Y and Z:
If X creates a record for this, the following transactions will be created by X and then later synchronised with Y's device:
X-Y-33-100-USD-Dinner-XYTrip-20S 40E-2025-12-03 18:00
X-Z-33-100-USD-Dinner-XYTrip-20S 40E-2025-12-03 18:00
- Dominant language
- Dart
- Stars
- 20
- Forks
- 39
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from StabilityNexus/Zplit
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
StabilityNexus/Zplit#77 · 1 comment ·
-
[GOOD FIRST ISSUE] [MINOR BUG]: Website uses default starter favicon instead of official Zplit logoPossibly taken A pull request linked to this issue is open or already merged. Opengood first issue
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
StabilityNexus/Zplit#73 ·
-
[FEATURE]: Enhancement of Onboarding Screen and Low Res AssetsPossibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 61/100
StabilityNexus/Zplit#75 · 2 comments ·
-
[GOOD FIRST ISSUE]: Documentation Cleanup - Addition of Contribution.mdPossibly taken @Logic769 claimed this 20 days ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
StabilityNexus/Zplit#64 · 2 comments ·
-
gsoc
Difficulty 4/5 3-5 days Newbie friendliness 48/100
StabilityNexus/Zplit#56 ·
All issues in StabilityNexus/Zplit
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
🚀 [firebase_core] Bump Firebase C++ SDK (14.1.0 → 14.2.0)Possibly taken @SelaseKay claimed this today. OpenNeeds Attention type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
firebase/flutterfire#18977 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AlphaWaveSystems/flutter-probe#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ubuntu/app-center#2306 ·
Maintainers usually reply within 1 day