Stabilize future.unstable_skipActionErrorRevalidation #11769
Merged
+95
−19
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.
Stabilize the RR
unstable_skipActionErrorRevalidation
flag. This is used by single fetch but it's functionality is independent of single fetch and fairly straightforward so I don't see any reason to delay stabilizing it until single fetch stabilizes.Functionally, when this is enabled, actions that return/throw with a 4xx/5xx don't automatically trigger revalidation - see https://remix.run/docs/en/main/guides/single-fetch#revalidations