-
Notifications
You must be signed in to change notification settings - Fork 899
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
Fix RTDB typings used by compat #7422
Conversation
🦋 Changeset detectedLatest commit: 67dd5b5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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.
LGTM, thanks for catching this!
Size Report 1Affected ProductsNo changes between base commit (c29156a) and merge commit (c86e9ff).Test Logs |
Size Analysis Report 1Affected ProductsNo changes between base commit (c29156a) and merge commit (c86e9ff).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
Note: Firestore changes will be done in a separate PR: #7423
E2E tests failed TypeScript compat build:
https://github.com/firebase/firebase-js-sdk/actions/runs/5470942751
due to changes on the following PRs:
Firestore PR: #7310RTDB PR: #6541
The E2E tests install the staged NPM version of the
firebase
package and run some smoke tests. They failed on TypeScript compilation due to the following reasons:1) For Firestore, types were only updated in Firestore modular, which is expected, as we don't add new features to compat. However, compat wraps modular classes, and it ran into an error importing their types and then checking them against firestore-types, which it uses as its types package. I'm not sure why it uses firestore-types instead of importing types directly from@firebase/firestore
but that would be a future change. I did try it, but it's not a 1-to-1 correspondence, especially theFirebaseFirestore
instance type, which doesn't exist in modular.