• internal/config/config.go
  • Registers the new @typescript-eslint/prefer-literal-enum-member, @typescript-eslint/prefer-namespace-keyword, and @typescript-eslint/prefer-string-starts-ends-with rules.
  • Adds the corresponding rule implementations to the global rule registry.
• internal/plugins/typescript/rules/prefer_literal_enum_member/prefer_literal_enum_member.go
  • Implements the prefer-literal-enum-member rule to enforce the use of literal values in enum members.
  • Provides an option to allow bitwise expressions in enum values.
• internal/plugins/typescript/rules/prefer_literal_enum_member/prefer_literal_enum_member_test.go
  • Adds comprehensive test cases for the prefer-literal-enum-member rule, covering both valid and invalid scenarios.
• internal/plugins/typescript/rules/prefer_namespace_keyword/prefer_namespace_keyword.go
  • Implements the prefer-namespace-keyword rule to suggest using namespace instead of module for TypeScript modules.
  • Includes auto-fix functionality to automatically replace module with namespace.
• internal/plugins/typescript/rules/prefer_namespace_keyword/prefer_namespace_keyword_test.go
  • Adds test cases for the prefer-namespace-keyword rule, ensuring correct identification and auto-fixing of module declarations.
• internal/plugins/typescript/rules/prefer_string_starts_ends_with/prefer_string_starts_ends_with.go
  • Implements the prefer-string-starts-ends-with rule to suggest using String#startsWith and String#endsWith methods.
  • Provides auto-fix functionality to replace manual string comparisons with the suggested methods.
  • Includes an option to allow single element equality comparisons.
• internal/plugins/typescript/rules/prefer_string_starts_ends_with/prefer_string_starts_ends_with_test.go
  • Adds extensive test cases for the prefer-string-starts-ends-with rule, covering various string comparison patterns and options.
• packages/rslint/src/node.ts
  • Fixes a bug in IPC message length encoding to correctly handle non-ASCII characters, preventing protocol corruption.

• The pull request introduces three new TypeScript-specific linting rules, enhancing code quality and consistency.
• A bug fix ensures that rslint can reliably handle a broader range of characters in IPC communication.
• The new rules are accompanied by comprehensive test suites, ensuring their correct behavior and preventing regressions.

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.

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.