feat: server functions return RSC payload #93
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
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.
Server functions now return result in RSC payload. This helps with supporting multiple types of results (including binary formats) and also enables the new
reload()API which enables single-roundtrip mutation and page (or outlet) refresh by combining the server function result with the rendered component in a single RSC payload.Includes tests for multiple server function result types and documentation update to include
reload().This PR addresses an issue with server functions without a return value (
Promise<void>) and enhances the framework to be able to return a rendered component along with the server function return value discussed in #85.