-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
[Quest] Firebase 9 compatibility #178
Comments
Updated the original post for a more detailed plan |
Can this be closed? |
I originally plan to once Firebase 10 is released and I remove support for compat SDK. But technically, Firebase 9 is supported already in this addon so I'll try to re-review if this can be closed over the weekend. |
Do you have plans to add support Firebase 10? |
#325 v10 support released in 4.1.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's the game plan for this
ember-firebase-service
and use the compat SDK across the addon. See more details on it below.v2.0.0
for the breaking changesv3.0.0
when addon is 100% compat SDK free (timing might be on Firebase 10 release)Notes:
v2.0.0
you can slowly transition to use the modular SDK in your apps (see here). But in my experience, these transition process may vary and is limited. For common and simple usage of this addon, you may not find anything that will be able to make use of this combination of v8 and v9 SDK API.Remove dependency with
ember-firebase-service
Unfamiliar to some,
ember-firebase-service
exposes a service that representsfirebase.app.App
which is heavily used in this addon. Moving forward, this addon will have its ownfirebase
service but will marked as a private service like:In the future, the service will have no purpose in a pure Firebase modular SDK world, hence will be removed. This is the reason why I'll mark it as private, to discourage users from using it.
Users that are using the service should move away from it. Here's a sample migration path:
Instead, you can do:
Another small change is how the addon config env is being set up. Here's the migration path:
Will now be:
The text was updated successfully, but these errors were encountered: