leancodepl / leancodepl/advanced_forms
Persistence
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 18
- Forks
- 2
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 14
Description
Hi!
We really love how your package streamlines form building, however we've encountered an issue. Sometimes we need to invoke an external intent, which makes the Android Activity susceptible to be destroyed. I've researched the built-in Flutter persistence solutions, but it seems none of them really fit in this case, especially when using multiple subforms.
It would be very appreciated to hear how you guys solve this issue in your company or to get a persistence feature added to leancode_forms, for example using hydrated_bloc.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the package's form state handling alongside Flutter's built-in persistence options and the proposed hydrated_bloc approach. Define how persistence should work when an Android Activity is destroyed, including cases with multiple subforms; done requires an agreed feature scope and state restoration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart, flutter
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100