Fix server functions failing when called from backend code #4908
Conversation
This file contains hidden or 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
…P context Server functions can now be invoked directly from server-side code without requiring an HTTP request context. When called outside an HTTP handler, extractors will use default values instead of failing, matching the behavior of the old server_fn implementation. Closes DioxusLabs#4907
… called from backend Functions with no server extractors use Default::default() and work from backend code. Functions with extractors still require HTTP context. Closes DioxusLabs#4907
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes "No FullstackContext found" error when calling server functions from background workers or other non-HTTP contexts.
Makes extraction conditional - falls back to
Default::default()when no HTTP context exists.Closes #4907