[FDC init] Fix React template creation when launched from VS Code#9171
[FDC init] Fix React template creation when launched from VS Code#9171
Conversation
Summary of ChangesHello @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 enhances the Firebase Data Connect initialization process by modifying the React application creation to be non-interactive. This change prevents user prompts during the Highlights
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 attempts to make the Vite app creation non-interactive by adding the --no-interactive flag. However, this flag is not recognized by create-vite and will cause an error. My review includes a critical fix to correctly disable interactivity by specifying a complete template name, which I believe should be react-ts to align with the use of TypeScript elsewhere in the project.
Bug Scenario
While testing the "local onboard flow", I ran into this bug when click the "init" button.
create-vitecmd added additional prompts that made it work poorly for piped stdin when launched from VS Code.Tested