-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(http): use serializeBody
to support JSON payload in FetchBackend
#50776
Conversation
7ee46f0
to
7925440
Compare
serializeBody
to support JSON payload in FetchBackend
I would expect to see a test verifying code in this PR. |
`HttpRequest.serializeBody` was used in HttpXhrBackend. `fetch` also needs to serialize request body. Close angular#50775
@pkozlowski-opensource Thanks for comment. 😊 I adds test codes in XHR / Fetch both side. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@leo6104 thanks for the fix 👍
This PR was merged into the repository by commit a126cbc. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…ngular#50776) `HttpRequest.serializeBody` was used in HttpXhrBackend. `fetch` also needs to serialize request body. Close angular#50775 PR Close angular#50776
…ngular#50776) `HttpRequest.serializeBody` was used in HttpXhrBackend. `fetch` also needs to serialize request body. Close angular#50775 PR Close angular#50776
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #50775
What is the new behavior?
it correctly serialize request body (same behavior with HttpXhrBackend)
Does this PR introduce a breaking change?
Other information