Fullstack: Introduce serde_qs extractor for query string
#4829
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
bwskin
changed the title
serde_qs extractor for query stringserde_qs extractor for query string
bwskin
force-pushed
the
feat/serverfn-struct-qs-extractor
branch
from
e78d6f3 to
f43680f
Compare
bwskin
force-pushed
the
feat/serverfn-struct-qs-extractor
branch
from
f43680f to
91c3b00
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replaces axum::extract::Query with a custom extractor based on serde_qs.
axum::extract::Query uses the serde_urlencoded crate, while on the client side, Dioxus currently relies on serde_qs.
This mismatch causes unexpected behavior and prevents proper deserialization of structs passed as arguments to #[get] server functions.
With this change, it becomes possible to use any type that serde_qs can serialize in a query string.
This PR is a followup to #4827
It’s a bit unstructured at the moment, as the module is temporarily placed in the fullstack-server crate.
Suggestions on a better location for it are highly welcome.