Skip to content

refactor(firestore): [PQ] refactor CountIf, Replace, Unnest and rename Function#13594

Merged
bhshkh merged 2 commits intogoogleapis:feature/fs-pipeline-queriesfrom
bhshkh:feat/fspq-rename-function
Jan 13, 2026
Merged

refactor(firestore): [PQ] refactor CountIf, Replace, Unnest and rename Function#13594
bhshkh merged 2 commits intogoogleapis:feature/fs-pipeline-queriesfrom
bhshkh:feat/fspq-rename-function

Conversation

@bhshkh
Copy link
Copy Markdown
Contributor

@bhshkh bhshkh commented Jan 13, 2026

@bhshkh bhshkh requested review from a team January 13, 2026 18:47
@bhshkh bhshkh requested a review from a team as a code owner January 13, 2026 18:47
@product-auto-label product-auto-label Bot added the api: firestore Issues related to the Firestore API. label Jan 13, 2026
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @bhshkh, 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 introduces a refactoring of the CountIf aggregate function, making its usage more explicit by requiring a BooleanExpression and relocating its method definition to the appropriate interface. Concurrently, the Function interface has been renamed to FunctionExpression to standardize naming across the Firestore client libraries.

Highlights

  • Refactor CountIf Function: The CountIf aggregate function has been refactored to explicitly accept a BooleanExpression as its argument, enhancing type safety and clarity. Its corresponding method has been moved from baseExpression to the BooleanExpression interface.
  • Rename Function Interface: The Function interface has been renamed to FunctionExpression to improve consistency and align with naming conventions used in other Firestore SDKs.

🧠 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.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the CountIf aggregate function to be more type-safe by requiring a BooleanExpression, and renames the Function interface to FunctionExpression for consistency with other Firestore SDKs. The changes are well-implemented and improve the API's robustness and ergonomics. I've added a couple of suggestions to improve the clarity of the comments for the new CountIf function to better reflect its behavior.

Comment thread firestore/pipeline_aggregate.go Outdated
Comment thread firestore/pipeline_filter_condition.go Outdated
@bhshkh bhshkh requested a review from daniel-sanche January 13, 2026 19:00
@bhshkh bhshkh force-pushed the feat/fspq-rename-function branch from 514c659 to e113a56 Compare January 13, 2026 19:02
@bhshkh bhshkh changed the title refactor(firestore): [PQ] refactor CountIf and rename Function refactor(firestore): [PQ] refactor CountIf, Replace, Unnest and rename Function Jan 13, 2026
Copy link
Copy Markdown
Contributor

@daniel-sanche daniel-sanche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bhshkh bhshkh merged commit a18aca3 into googleapis:feature/fs-pipeline-queries Jan 13, 2026
8 checks passed
@bhshkh bhshkh deleted the feat/fspq-rename-function branch January 13, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: firestore Issues related to the Firestore API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants