-
Notifications
You must be signed in to change notification settings - Fork 897
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
Add Provider.initialize()
#4595
Conversation
🦋 Changeset detectedLatest commit: 164a4e3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 34 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approval for auth
Binary Size ReportAffected SDKs
Test Logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for perf, thanks!
Changeset File Check
|
Currently component factory doesn't take an options parameter. This leads to a 2 steps initialization pattern in
initializeAuth()
,initializeFirestore()
,initializePerformance()
andinitializeAnalytics()
:Step 1: The component framework creates a service instance using default options
Step 2: Set user supplied options on the service instance returned from Step 1.
This PR removes the need of the second step by allowing you to pass an options to the component framework
using the new
Provider.initialize()
method.2 steps initialization is also problematic for certain use cases. See this doc for more details.
Changes
Component factory can take an options parameter now:
Use
initialize()
to initialize with options. TakinginitializePerformance()
as an example: