8000 [FDC] Fix a small bug where `firebase deploy` didn't include GQL in folders by fredzqm · Pull Request #8981 · firebase/firebase-tools · GitHub
[go: up one dir, main page]

Skip to content

Conversation

fredzqm
Copy link
Contributor
@fredzqm fredzqm commented Aug 15, 2025

Tested connector with nested file.

  1. firebase init dataconnect
  2. firebase deploy
  3. View in console
  4. firebase init dataconnect to download them

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.

Summary of Changes

Hello @fredzqm, 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 addresses a bug where firebase deploy was failing to correctly include GraphQL files located within subdirectories. The fix involves updating the file utility functions to recursively discover all .gql and .graphql files, ensuring that the deployment process correctly identifies and bundles all necessary GraphQL schema definitions, regardless of their folder depth.

Highlights

  • Recursive GQL File Discovery: The readGQLFiles function in src/dataconnect/fileUtils.ts has been updated to utilize the glob library. This change enables the function to recursively search for and include all .gql and .graphql files located within the specified source directory and its subfolders, addressing the previous limitation where only top-level files were recognized.
  • Path Handling Refinement: The toFile helper function was adjusted to correctly process the full file paths returned by the glob utility. It now internally calculates the relative path from the source directory, ensuring proper file referencing within the system.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 fixes a bug where GraphQL files in subdirectories were not included during firebase deploy. The change correctly uses glob to find all .gql and .graphql files recursively. My feedback focuses on improving the usage of the glob library to make it more robust and secure, especially on different operating systems.

@fredzqm fredzqm requested a review from joehan August 15, 2025 23:21
fredzqm and others added 3 commits August 17, 2025 18:10
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
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, just add a changelog

@fredzqm fredzqm enabled auto-merge (squash) August 18, 2025 19:29
@fredzqm fredzqm merged commit 2e14b2d into master Aug 18, 2025
77 of 78 checks passed
@fredzqm fredzqm deleted the fz/fdc-nested-gql branch August 18, 2025 20:26
@github-project-automation github-project-automation bot moved this from Approved [PR] to Done in [Cloud] Extensions + Functions Aug 18, 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.

2 participants
0