feat(fetch): support form data and form url encoded request #1529
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
soartec-lab
added
enhancement
anymaniax
approved these changes
Jul 21, 2024
melloware
approved these changes
Jul 21, 2024
|
It seems like there is an issue with this - If not the boundaries will not be properly set. |
This was referenced Jul 22, 2024
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.
Status
READY
Description
follow up #1387
fix #1525
I made the
fetchclient support cases other thanapplication/json, such asmultipart/form-dataandapplication/x-www-form-urlencoded. And, if inputOpenAPIhavecontent-type, addContent-Typeheader to fetch request options.Related PRs
none
Todos
Steps to Test or Reproduce
You can check from the test case I added