Skip to content

Add Firestore to FriendlyMeals#164

Merged
jhuleatt merged 34 commits intomainfrom
jhuleatt-firestore-friendlymeals
Feb 2, 2026
Merged

Add Firestore to FriendlyMeals#164
jhuleatt merged 34 commits intomainfrom
jhuleatt-firestore-friendlymeals

Conversation

@jhuleatt
Copy link
Collaborator

The web version of #159

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jhuleatt, 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 significant overhaul of the web application's user interface and styling system. It integrates shadcn/ui components and Tailwind CSS, establishing a modern, utility-first approach to UI development. This foundational change prepares the project for more streamlined and consistent UI implementation, despite the PR title suggesting Firestore integration, which is not reflected in the code changes.

Highlights

  • UI Framework Adoption: The project now utilizes shadcn/ui components, providing a set of accessible and customizable UI building blocks.
  • Tailwind CSS Integration: Tailwind CSS has been implemented as the primary styling framework, replacing traditional CSS with a utility-first methodology.
  • Theming System: A comprehensive theming system, including light and dark mode support, has been established using CSS variables, aligning with shadcn/ui's approach.
  • Developer Experience Enhancements: New utility functions (cn) and TypeScript path aliases (@/*) have been added to improve class management and module resolution, respectively.
  • Dependency Updates: package.json and package-lock.json have been updated to reflect the addition of numerous UI-related libraries and their transitive dependencies.

🧠 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
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 sets up the web project with Tailwind CSS and shadcn/ui, which is a great choice for building modern UIs. The changes include adding necessary dependencies, configuring Tailwind, and setting up TypeScript path aliases for better module resolution. The code looks solid and follows standard practices for this kind of setup.

I've made a few minor suggestions regarding file formatting to ensure consistency and prevent potential issues with some development tools.

While the PR title mentions Firestore, the changes seem focused on the UI setup. This is perfectly fine, but it might be worth clarifying if this is part of a larger feature, or if the title could be updated to better reflect the content of this specific PR (e.g., 'feat: Add Tailwind CSS and shadcn/ui').

}
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

It's a good practice to end files with a newline character. Some tools might have issues with files that don't end with a newline.

}

"include": [
"src"
]
} No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

It's a good practice to end files with a newline character. Some tools might have issues with files that don't end with a newline.

Suggested change
}
}

]
}
}
} No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

It's a good practice to end files with a newline character. Some tools might have issues with files that don't end with a newline.

Suggested change
}
}

@jhuleatt jhuleatt marked this pull request as ready for review January 28, 2026 16:02
@jhuleatt jhuleatt requested a review from morganchen12 January 28, 2026 16:02
Copy link
Contributor

@morganchen12 morganchen12 left a comment

Choose a reason for hiding this comment

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

@jhuleatt jhuleatt merged commit 4839a7f into main Feb 2, 2026
3 checks passed
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

Comments