Clarify when Effects are needed for data fetching (#8226) #8238
+6
−0
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.
This PR improves the explanation in the "Fetching data" section of "You Might Not Need an Effect" to clarify when an Effect is needed versus when it's not.
The previous text was confusing because it said "You don't need to move this fetch to an event handler" which seemed contradictory given the page's title. This change:
This makes it clearer for readers to understand when Effects are appropriate for data fetching.
Closes #8226