Make serde optional by introducing query, form features, and re-working WASM header parsing
#2858
+116
−39
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
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.
Resolves #2823
These changes allow using reqwest without
serde(and evensynfor a good number of features).First commit wraps the
RequestBuilder::query()andRequestBuilder::form()methods in new feature flags:query,form. These features are enabled by default, so the change would only impact anyone settingdefault-features = false.Second commit removes the use of
serde_jsonfor WASM header parsing, instead using JS array access.Technically this still pulls in
serdedue to a bug inurl, but that should be resolved in the next release.