Replies: 2 comments 7 replies
-
I had some thought on this, and could be interesting: What about allowing a |
Beta Was this translation helpful? Give feedback.
-
How was the RearchConsumer “not refreshing” when you passed it new constructor parameters? In order to get the new constructor parameters it’d have to be rebuilt, wouldn’t it? It’s completely fine to pass in data via the constructor, and it shouldn’t require any extra handling |
Beta Was this translation helpful? Give feedback.
-
So, In my way back to
rearch_flutter
I had a problem for 30 minutes trying to figuring out why aRearchConsumer
was not refreshing, and it was because I was passing it data on its constructor (like with State(less/ful)Widgets).So my question is what would be the preferred way to handle a situation when you need a
RearchConsumer
but also you need to pass it some values (that could change over the time) via its constructor?Would you advice against that "mixin" even if you know the passed values should not change over the time?
Beta Was this translation helpful? Give feedback.
All reactions