Replies: 1 comment 2 replies
-
Ignoring new values is anti-pattern. What's the goal? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Like many on Flutter, we're using Firestore for our backend.
By default we have document / collection streams, ie:
Most of the time we want realtime behaviour:
Occasionally we'd just like the most recent value, and don't want to rebuild on subsequent yields.
The above example uses streams, but the question would apply to computed providers too, ie:
We'd benefit for not having to duplicate our stream logic for equivalents with futures. I think this would be more pronounced with the computed providers.
Beta Was this translation helpful? Give feedback.
All reactions