-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ensure server action errors notify rejection handlers #61588
Merged
ztanner
merged 1 commit into
canary
from
02-02-ensure_server_action_errors_notify_rejection_handlers
Feb 2, 2024
Merged
ensure server action errors notify rejection handlers #61588
ztanner
merged 1 commit into
canary
from
02-02-ensure_server_action_errors_notify_rejection_handlers
Feb 2, 2024
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
ijjk
added
area: tests
created-by: Next.js team
PRs by the Next.js team.
type: next
labels
Feb 2, 2024
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ztanner
force-pushed
the
02-02-ensure_server_action_errors_notify_rejection_handlers
branch
from
February 2, 2024 19:04
58afd09
to
a9af51a
Compare
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
Next Runtimes
Diff detailsDiff for page.jsDiff too large to display Diff for 68-HASH.jsDiff too large to display |
ztanner
requested review from
timneutkens,
ijjk,
shuding,
huozhi,
feedthejim and
wyattjoh
as code owners
February 2, 2024 19:14
shuding
approved these changes
Feb 2, 2024
ztanner
deleted the
02-02-ensure_server_action_errors_notify_rejection_handlers
branch
February 2, 2024 22:36
EXCITING !!! I HAVE WAITING FOR LONG TIME |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What
When attaching a rejection listener to a server action promise, in the case of network errors, the rejection handler would be skipped and it'd throw an error that crashes the application.
Why
When we refactored these reducers to no longer suspend, it caused the rejection handling logic we have to no longer make sense. In this case we're working with a native promise that won't have a
status
property, so we'd re-throw the error and not callreject
.How
This removes the special status handling logic and makes the rejection handler always call
reject
with the error. This will either be handled by user code or let the error bubble to an error boundary.I also cleaned up some mutable code that is no longer needed now that these reducers aren't replayed.
Closes NEXT-1715
Closes NEXT-2323
Fixes #58638