Replies: 3 comments 6 replies
-
Why not use consumer only? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Your link is down |
Beta Was this translation helpful? Give feedback.
2 replies
-
I reached a solution. Is the case (2.). It wasn't as complicated as I thought. Anyway, I'm open to better solutions.
|
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a CustomState that I have been ussing in most of my Flutter stateful widget for a while.
Today I started with Riverpod. I will have to use ConsumerState. So my dilema is to choose one solution. Possible solutions:
For me it would be perfect choice but I think it is not possible due to the constructor data. (Yes, that data could maybe refactored into
abstract getter functions, but I don't know yet if this solution is possible).
and if adding Riverpod in all my projects, even if they didn't use it, would affect the performance.
Any help, advice or other possible solution are appreciated.
Beta Was this translation helpful? Give feedback.
All reactions