You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fetch API defines the global fetch() method for getting resources (modern replacement of XMLHttpRequest which the sdk currently uses internally). Due to browser adoption and usage we won't be able to use it internally any time soon without a polyfill which itself depends on a polyfill for promises. Too much bloat.
But the fetch spec also defines Request, Response, and Headers objects. The sdk has it's own internal representation of those concepts. It might be useful to implement them according to the fetch spec. Though this would be a breaking change since responses are exposed to the developer.
The text was updated successfully, but these errors were encountered:
The fetch API defines the global
fetch()
method for getting resources (modern replacement of XMLHttpRequest which the sdk currently uses internally). Due to browser adoption and usage we won't be able to use it internally any time soon without a polyfill which itself depends on a polyfill for promises. Too much bloat.But the fetch spec also defines Request, Response, and Headers objects. The sdk has it's own internal representation of those concepts. It might be useful to implement them according to the fetch spec. Though this would be a breaking change since responses are exposed to the developer.
The text was updated successfully, but these errors were encountered: