chore(dev): update vscode settings for typescriptreact

[rohit-4321]

Related Issue:

Fix #19909

Description

This PR updates the development environment configuration to ensure .tsx files are formatted correctly.

Changes:

• Dev: Added [typescriptreact] to .vscode/settings.json to set Prettier as the default formatter for React TypeScript files.

[gemini-code-assist]

Summary of Changes

Hello @rohit-4321, I'm Gemini Code Assist¹! 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 development environment by ensuring consistent code formatting for TypeScript React files within VS Code. By explicitly setting Prettier as the default formatter for .tsx files, it standardizes code style, reduces formatting discrepancies, and improves overall code readability for the project.

Highlights

• VS Code Configuration: Configured Prettier as the default formatter for [typescriptreact] files in .vscode/settings.json.

Changelog

• .vscode/settings.json
  • Added a new configuration entry for [typescriptreact] to specify Prettier as the default formatter.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the .vscode/settings.json file to include a formatter configuration for typescriptreact. This ensures that .tsx files are consistently formatted using the Prettier extension, matching the existing setup for standard TypeScript files. The change is correct and follows VS Code configuration standards for React-based TypeScript projects.

[gemini-code-assist]

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.

[gemini-code-assist]

Code Review

The pull request correctly updates the .vscode/settings.json file to include [typescriptreact] for Prettier formatting, which aligns with the project's technology stack (TypeScript and React). This change ensures consistent code formatting for .tsx files within VS Code, improving maintainability and adherence to the project's coding style.

[gemini-code-assist]

This addition correctly configures Prettier as the default formatter for .tsx files. This aligns with the project's stated main technologies (TypeScript and React) and the development convention to adhere to existing patterns and coding style (Repository Style Guide, line 73). This ensures consistent formatting across the codebase for React components written in TypeScript.

References

1. Adhere to existing patterns in packages/cli (React/Ink) and packages/core (Backend logic). ^(link)

[rohit-4321]

/gemini review

[gemini-code-assist]

I've already provided my review on this change. If you have any specific technical questions about my previous comment or the code, please let me know.

[rohit-4321]

cc @bdmorgan (tagging for better visibility)

[jacob314]