[FEATURE]: Setup Bloc State Management Layer
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by locating the app’s existing feature structure and Drift SQLite database setup, then read the Bloc documentation and inspect how Balance, Group, Transaction, and User data are represented. The issue calls for Events, States, and Repositories for all four features, but does not identify files or define specific behaviors; completion means these features use the Bloc layer to load and manage local data.
Written by the indexing model from the issue text.
Description
Feature and its Use Cases
Setup the Bloc architecture for the Zplit app to manage state across all core features.
What is the feature?
Bloc state management layer with Events, States, and Repositories for Balance, Group, Transaction, and User features.
How would users benefit from it?
Provides a clean, reactive, and testable state management foundation for all app features.
What scenarios would this feature address?
Loading, updating, and managing local data from the Drift SQLite database through a structured Bloc pattern.
Additional Context
No response
Code of Conduct
- I have joined the Discord server and will post updates there
- I have searched existing issues to avoid duplicates
- 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