Initial-load fetchers should not automatically revalidate on GET navigations #10688
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.
Follow up to #10623 which inadvertently started revalidating initial-load fetchers on GET navigations, when it should only revalidate (without calling
shouldRevalidate
) on explicit revalidations (submissions,useRevalidate
, etc.).Discord thread in which this was raised: https://discord.com/channels/770287896669978684/1128075241579614208/1128080680417501215