Fetch API #1610
Merged
Fetch API #1610
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
rauenzi
requested changes
Apr 13, 2023
|
Could you also add the deprecation notices to the polyfill calls? |
Diegiwg
approved these changes
Apr 30, 2023
Diegiwg
approved these changes
May 2, 2023
|
@Diegiwg why? |
rauenzi
approved these changes
Jun 15, 2023
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.
Adds
BdApi.fetch()api which is equivalent design of the globalfetch()api but it can bypass CSP. This also introduces the deprecation ofrequire("https")/require("request")as well.It also adds the ability to add a body to requests using current
require("https")polyflll, reason being not much effort required to implement this.