Conversation
…inquirer, generate-schema, lodash)
…nge-tracker-dependencies chore(firestore-bigquerychange-tracker): cleanup dependencies
sync next with master
Adding --provenance flag
Updating to a newer version of node
Change repository.url
…extension version Updates functions to use @firebaseextensions/firestore-bigquery-change-tracker v2 and increments the extension release version to 0.2.11 with corresponding changelog notes. Made-with: Cursor
…tracker bump Updates functions/package-lock.json for @firebaseextensions/firestore-bigquery-change-tracker@2.0.0 and normalizes LOG_LEVEL to the stricter tracker config type required during build. Made-with: Cursor
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request delivers updates across two Firebase extensions. The Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces updates for two extensions, firestore-bigquery-export and firestore-send-email.
For firestore-bigquery-export, the version is updated to 0.2.11, primarily to upgrade the firestore-bigquery-change-tracker dependency to v2. This change also cleans up the project by removing several unused dependencies. A new function for normalizing log levels has been added, and I've provided a suggestion to make it more robust.
For firestore-send-email, the version is bumped to 0.2.7, adding support for customArgs and ipPoolName in SendGrid options. This is a valuable feature enhancement, and the implementation, including new tests and documentation, appears to be thorough and correct.
…packed files Publish nested partitioning files in the package tarball so BigQuery export can resolve runtime imports when testing this RC. Made-with: Cursor
… test linking The prerelease version 2.0.1-rc.0 does not satisfy downstream ^2.0.0 ranges, which can make CI resolve the published 2.0.0 package instead of the local workspace package. Made-with: Cursor
…ude nested build artifacts
…er to version 2.0.1 in package-lock.json
…rt-package-json-change fix(firestore-bigquery-change-tracker): update dependency to version to 2.0.1
* refactor(firestore-bigquery-change-tracker): improve partitioning types and clean up exports
- Replace flat config with PartitioningStrategy discriminated union for type-safe partitioning
- Rename Config to ChangeTrackerConfig for clarity
- Export PartitioningStrategy, PartitioningFieldType, TimePartitioningGranularity
- Remove unused dependencies (generate-schema, inquirer, lodash)
- Bump version to 2.0.1
* chore(firestore-bigquery-change-tracker): bump to 2.0.2
* fix(firestore-bigquery-change-tracker): address PR feedback
- Use explicit { granularity: "NONE" } default instead of empty object
- Add deprecated Config alias for backwards compatibility
* test(firestore-bigquery-change-tracker): re-add tests for malformed partitioning configs
* fix(firestore-bigquery-change-tracker): throw on invalid partitioning strategy instead of silent fallback
* revert(firestore-bigquery-change-tracker): keep NONE fallback for invalid partitioning configs
Update the extension functions package to consume @firebaseextensions/firestore-bigquery-change-tracker@2.0.2. Made-with: Cursor
…ms for change-tracker 2.x (#2698) * fix(firestore-bigquery-export): implement buildPartitioningConfig function and update tests * fix(tests): improve readability and structure of partitioning tests * chore(firebase-bigquery-export): release version 0.3.0 with breaking changes and improved partitioning validation
…x a small bug (#2699) * fix: cover all possible partitioning configurations with tests and fix small bug * refactor: make partitioning tests more DRY
7 participants
No description provided.