Conversation
|
Summary of ChangesHello @milaGGL, 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 expands the array processing capabilities within the Firestore SDK by adding eight new expressions. These functions provide developers with enhanced tools to extract specific elements (first, last, or a specified number of elements) and calculate statistical values (minimum, maximum, or a specified number of min/max elements) directly from arrays within their data pipelines, streamlining array-based data transformations. 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. Changelog
Activity
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. 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces eight new array expression functions to Firestore pipelines, enhancing the query capabilities for array fields. The new functions are arrayFirst, arrayFirstN, arrayLast, arrayLastN, arrayMaximum, arrayMaximumN, arrayMinimum, and arrayMinimumN. The changes are well-implemented and include corresponding API definitions, documentation, and comprehensive tests. I have identified a few areas for improvement, primarily concerning API documentation consistency and formatting in the generated documentation files.
There was a problem hiding this comment.
Code Review
This PR introduces a comprehensive set of new array expressions for Firestore pipelines, including functions for filtering, slicing, and finding elements within arrays. The implementation is well-tested with extensive integration tests. My feedback is primarily focused on improving the accuracy and consistency of the documentation for these new features to ensure clarity for developers. I've pointed out a few places where examples are missing or descriptions of return values could be more precise based on the test cases.
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces a comprehensive set of new array expressions to Firestore pipelines, which is a great feature enhancement. The implementation and tests are thorough. My feedback is mainly focused on improving code organization, documentation clarity, and minor code simplification for better maintainability. I've pointed out some redundant function calls, suggested reordering of exports and methods for consistency, and highlighted some areas in the documentation that could be confusing for users due to duplicated entries and incorrect links.
| arrayIndexOf, | ||
| arrayLastIndexOf, | ||
| arrayIndexOfAll, | ||
| arrayFilter |
There was a problem hiding this comment.
nit: i think these should be grouped with the other array exports.
|
|
||
| // @beta | ||
| export function arrayFilter(fieldName: string, variable: string, predicate: Expression): FunctionExpression; | ||
| export function arrayFilter(fieldName: string, variable: string, predicate: BooleanExpression): FunctionExpression; |
There was a problem hiding this comment.
What about naming the variable alias in arrayFilter? It may not matter much in the JS SDK, but it would be helpful when porting to Swift, since it would become a labeled parameter there. https://www.hackingwithswift.com/sixty/5/4/parameter-labels
Add new array expressions
arrayFirst,arrayFirstN,arrayLast,arrayLastN,arrayMinimum,arrayMinimumN,arrayMaximum,arrayMaximumN,arrayFilter,arraySlice,arrayIndexOf,arrayLastIndexOf,arrayIndexOfAll.NOTE: Do not merge as
arrayFilterneeds to be updated.