I am now becoming a huge fan of Riverpod in π₯π
I have been updating this app with Clean Architecture and .
github.com/rodydavis/clea
It is really nice to abstract dependencies not worrying about the BuildContext.
cc
Conversation
Replying to
One think I have been loving is being able to define the abstract class and implementation separately. π οΈ
I also have been putting test files next to source in the lib folder. π€
1
2
The fact that I can have compile time errors is huge and now want to make them for more things like view models.
I have resisted a MVVM style for a long time but I think that there is valid use cases for it.
Like being able to update the ui without changing any logic.
1
2
I keep finding myself spending to much time refactoring code based on frameworks, but really working to decouple.
Ideally the view is an implementation detail and if I wanted to reuse the dart logic for a CLI app or html then it should be easy to connect.
1
3
Another nice thing about the abstract class + implementation approach is being able to use the import assertions to load the IO or HTML based version at runtime.
4
If youβre concerned about Context in your Clean Architecture, there is something stranger on your code.
1
I was referring to accessing a model in the init state with provider.
Is there a reason why you decided not to use a ConsumerWidget instead of a StatelessWidget here?
1
Iβm updating an existing fork! Iβm also fixing stuff like that
1
2
Show replies
Cool to have you seeing the light with Riverpod too πIt really is nice to use it ππ
1
8




