Skip to content

Conversation

samedson
Copy link
Contributor

No description provided.

Copy link
Contributor

Summary of Changes

Hello @samedson, 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 enhances the developer experience within the Firestore initialization guide by providing clearer and more actionable instructions for verifying database setup. It specifically advises developers to run their local development application in a separate terminal and offers a practical tip for identifying the correct run command, particularly for web projects, thereby improving the overall testing workflow.

Highlights

  • Improved Developer Guidance: The Firestore initialization guide now includes explicit instructions for developers to run their local application for testing purposes. This enhancement aims to streamline the verification process by ensuring developers actively test their app's functionality against the newly set up Firestore.
  • Practical Testing Suggestions: Added a practical tip suggesting developers check their package.json file for web applications to find the appropriate command to run their development environment, making the guidance more actionable and user-friendly.
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
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 updates the Firestore initialization guide to suggest how to run the development application for testing. My review includes two points:

  1. A high-severity concern about a potential contradiction between this guide and the init_backend.ts guide regarding when the application should be run for testing.
  2. A medium-severity suggestion to make the instructions more comprehensive by including examples for running the app on different platforms, not just web.

- Only proceed with verification after successfully running \`firebase deploy --only firestore\`
- Guide the user to visit \`https://console.firebase.google.com/u/0/project/{PROJECT_ID}/firestore\` where \`{PROJECT_ID}\` is the project they're currently using (or use \`_\` if project id is unknown).
- Have developers test their application functionality and verify test data appears in the console
- Have developers test their application functionality and verify test data appears in the console. Ask them to run a local version of their app in a separate terminal and suggest the command to run their dev app. For example, for web apps you can check their \`package.json\` to see how to run their app.
Copy link
Contributor

Choose a reason for hiding this comment

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

high

There appears to be a contradiction with the instructions in src/mcp/resources/guides/init_backend.ts. Line 22 of that file states, "Do not run the app until you have completed all 3 guides" (which includes Firestore). However, this change adds instructions to run the app after setting up only Firestore. This conflicting guidance could confuse the agent. Please clarify the intended workflow and ensure the guides are consistent.

Copy link
Contributor

Choose a reason for hiding this comment

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

WDYT about just removing that line about not running until all guides are done? Seems like that line would be a problem as we add other services anyway

Copy link
Contributor

Choose a reason for hiding this comment

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

Gemini should run the app for them and provide the link to open the app on the browswer.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed both of these

- Only proceed with verification after successfully running \`firebase deploy --only firestore\`
- Guide the user to visit \`https://console.firebase.google.com/u/0/project/{PROJECT_ID}/firestore\` where \`{PROJECT_ID}\` is the project they're currently using (or use \`_\` if project id is unknown).
- Have developers test their application functionality and verify test data appears in the console
- Have developers test their application functionality and verify test data appears in the console. Ask them to run a local version of their app in a separate terminal and suggest the command to run their dev app. For example, for web apps you can check their \`package.json\` to see how to run their app.
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The example for running the dev app is specific to web applications. To make this instruction more comprehensive for the agent, which supports multiple platforms, it would be beneficial to include examples for other environments like Android and Flutter.

- Have developers test their application functionality and verify test data appears in the console. Ask them to run a local version of their app in a separate terminal and suggest the command to run their dev app. For example, for web apps check their `package.json` for a "start" or "dev" script; for Android apps, they can run from Android Studio; and for Flutter apps, they can use `flutter run`.

Copy link
Contributor

Choose a reason for hiding this comment

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

Seems like a good clarification to me, wdyt?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added this

Copy link
Contributor

@joehan joehan left a comment

Choose a reason for hiding this comment

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

LGTM in general, tho GCA's comments seem to be worth addressing

- Only proceed with verification after successfully running \`firebase deploy --only firestore\`
- Guide the user to visit \`https://console.firebase.google.com/u/0/project/{PROJECT_ID}/firestore\` where \`{PROJECT_ID}\` is the project they're currently using (or use \`_\` if project id is unknown).
- Have developers test their application functionality and verify test data appears in the console
- Have developers test their application functionality and verify test data appears in the console. Ask them to run a local version of their app in a separate terminal and suggest the command to run their dev app. For example, for web apps you can check their \`package.json\` to see how to run their app.
Copy link
Contributor

Choose a reason for hiding this comment

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

Gemini should run the app for them and provide the link to open the app on the browswer.

@joehan joehan enabled auto-merge (squash) October 1, 2025 16:27
@joehan joehan merged commit 980f161 into master Oct 1, 2025
47 of 48 checks passed
@joehan joehan deleted the samedson-dev-app-run branch October 1, 2025 16:42
@github-project-automation github-project-automation bot moved this from Approved [PR] to Done in [Cloud] Extensions + Functions Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants