refactor!: rework app init flow and credential management #105
+669
−93
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.
This PR aims to align the app API more closely with Node. Changes:
FirebaseAdminAppis now has a private constructor.FirebaseAdminclass exists, with staticinitalizeApp+getAppsetc methodsinitalizeAppare now all optional, whereas right now they are requiredAppOptions(should probably name thisFirebaseAppOptions(?), inline with the node sdk. This also adds support for some missing options such as storage bucket which we'll need.projectId(now inside ofAppOptions) will always exist. Like node, it first checks for a user provided value, then the credential (if its a service account), then finally the environment. Which allows no options toinitalizeApp, for use on GCP environments.ServiceAccountCredentialorApplicationDefaultCredential, which is used to detect the projectId.