-
Notifications
You must be signed in to change notification settings - Fork 938
Switched firebase/database to use the fetch()
api
#9046
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: ce3da16 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
I am a bit intrigued by this part "better-supported" |
Yeah I could've worded that better. Essentially - correct me if I'm wrong - but in modern cases, fetch is supported in all contexts where Long story short: By 'better supported', I simply mean there's slightly more environments where the Fetch API is officially adopted & supported. |
gotcha, tnx for the explanation |
Oh right yeah. As mentioned, fetch has slightly better support across platforms and an arguably more readable API. This PR intends to switch |
Switched out the usage of
XMLHttpRequest
in @firebase/database for primitives from the more modern and better-supported Fetch API.