Allow instance-id to auto-generate typings, separate internal vs external APIs #969
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.
Unfortunately, I merged the previously approved #965 into the wrong branch as I forgot to change the target before merging. Otherwise, this is an identical PR.
Side-note: If you merge a PR, and then revert, you cannot re-open the PR like you can for issues (lesson learned).
Context
The goal is to bridge the gap between today's Admin SDK (manually curated d.ts files, nested namespaces) and a modularized SDK that has auto-generated typings.
This is the second milestone from:
go/firebase-node-auto-typing
.Goals for this PR
Prerequisites
The intention for this PR is to be merged after RTDB modularization.The gulpfile PR from
hlazu-modularizing-gulpfile
.Test Plan