Make Fetch integration test handle UTF-8 content #13551
Draft
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
- Move test away from external endpoints (uses test web server) - Validate UTF-8 `fetch` handling
… OfficeDev/office-js/4736-utf8sample
auto-merge was automatically disabled
August 10, 2024 00:22
Pull request was converted to draft
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.
Description
Update the content and remote endpoint for the
fetchDesktop integration test.Type of Change
Why
fetch/ Blob implicit non-ASCII text response handling.What
fetch.Related to OfficeDev/office-js#4736
Testing
Microsoft Reviewers: Open in CodeFlow