-
Notifications
You must be signed in to change notification settings - Fork 0
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
State Management with Cubit #2
Comments
I don't know if i should staying with cubit / mono-state, or go riverpod. With input from companies, riverpod seems better |
dleurs
pushed a commit
that referenced
this issue
May 26, 2023
Cubit seems finally easier for the starter because :
|
dleurs
pushed a commit
that referenced
this issue
May 31, 2023
dleurs
pushed a commit
that referenced
this issue
May 31, 2023
dleurs
pushed a commit
that referenced
this issue
May 31, 2023
dleurs
pushed a commit
that referenced
this issue
May 31, 2023
dleurs
pushed a commit
that referenced
this issue
May 31, 2023
dleurs
pushed a commit
that referenced
this issue
May 31, 2023
dleurs
pushed a commit
that referenced
this issue
Jun 1, 2023
dleurs
pushed a commit
that referenced
this issue
Jun 1, 2023
Should I keep usecase ? or only use usecase when intelligence required in several cubits ? |
dleurs
pushed a commit
that referenced
this issue
Jul 10, 2023
done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
State Management with RiverPod
Want to do it in a mono-state way
I think I will do :
Riverpod will also be used to do navigation 2.0 with beamer and example slovnicki/beamer#601
I will try to do as little code generation as possible to avoid building app taking 5 min or more when big
The text was updated successfully, but these errors were encountered: