Skip to content
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.

Sign up for GitHub

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

Jump to bottom

State Management with Cubit #2

Closed
dleurs opened this issue May 26, 2023 · 4 comments
Closed

State Management with Cubit #2

dleurs opened this issue May 26, 2023 · 4 comments

Comments

@dleurs
Copy link
Owner

dleurs commented May 26, 2023

State Management with RiverPod

Want to do it in a mono-state way

I think I will do :

  • The counter app

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
@dleurs
Copy link
Owner Author

dleurs commented May 26, 2023 •
edited
Loading

I don't know if i should staying with cubit / mono-state, or go riverpod.

With input from companies, riverpod seems better

https://www.youtube.com/watch?v=EPVKdverFuw

dleurs pushed a commit that referenced this issue May 26, 2023
feat(#2): Setting up pubspec.yaml for riverpod
52d1657
@dleurs
Copy link
Owner Author

dleurs commented May 30, 2023

Cubit seems finally easier for the starter because :

  • Already worked with it in Tape à l'Oeil app
  • Seems more straight forward, less space for weird config / bugs
  • Recommanded for teams

https://mobileappcircular.com/bloc-vs-riverpod-making-the-right-choice-for-your-flutter-app-5feb4486ac4

@dleurs dleurs changed the title State Management with RiverPod State Management with Cubit May 30, 2023
dleurs pushed a commit that referenced this issue May 31, 2023
feat(#2 #3): first step implementing state management for fruit api
4dbf040
dleurs pushed a commit that referenced this issue May 31, 2023
feat(#2 #3): screen with fruits now visible
400e748
dleurs pushed a commit that referenced this issue May 31, 2023
doc(#2 #3): Improved doc adding endpoint and minor fix inside code
b30f850
dleurs pushed a commit that referenced this issue May 31, 2023
doc(#2 #3): Improved doc images
7a0692c
dleurs pushed a commit that referenced this issue May 31, 2023
feat(#2 #3): Improved doc images and maxline set to 120. 80 is too short
973dcaf
dleurs pushed a commit that referenced this issue May 31, 2023
feat(#2 #3): Cleaning code, merge request review
c70a058
dleurs added a commit that referenced this issue May 31, 2023
@dleurs
Merge pull request #6 from dleurs/develop
17ecf00 
Megre develop into main feat(#2 #3)
@dleurs dleurs closed this as completed Jun 1, 2023
dleurs pushed a commit that referenced this issue Jun 1, 2023
docs(#2 #3): Improving README, UI should have no intelligence
bf9b6e4
dleurs pushed a commit that referenced this issue Jun 1, 2023
docs(#2 #7): Start docs about fruit tests
025b2d6
@dleurs
Copy link
Owner Author

dleurs commented Jul 6, 2023

Should I keep usecase ? or only use usecase when intelligence required in several cubits ?

@dleurs dleurs reopened this Jul 6, 2023
dleurs pushed a commit that referenced this issue Jul 10, 2023
@DimitriLeursRexel
fix(#2 #13): fix api using fromJson and not fromMap
5b83906
@dleurs
Copy link
Owner Author

dleurs commented Jul 13, 2023

done

@dleurs dleurs closed this as completed Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dleurs