Clarify the use of useFuture #408
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kwill39
force-pushed
the
use-future-docs
branch
from
0b6ed1e
to
f9103ae
Compare
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe what scenario you think is uncovered by the existing examples/articles
Document that Futures should not be created inside
useFuture(see #132 & #119)Describe why existing examples/articles do not cover this case
useFuturebehaves likeFutureBuilder. This is not explicitly stated but rather implied through an understanding of Flutter Hooks. This understanding may not be intuitive for new users and can lead to a misunderstanding about the behavior ofuseFuture.