feat(fuzzy-finder): add table completion for MUTATE statement

[apstndb]

Summary

Add fuzzy table completion to the MUTATE statement, so MUTATE <Ctrl+T> triggers fuzzy table selection.

Key Changes

• client_side_statement_def.go: Add Completion field with fuzzyCompleteTable to the MUTATE statement definition
• fuzzy_finder_test.go: Add test cases for MUTATE table completion (trailing space and partial table name)

Test Plan

• make check passes
• Manual testing completed — MUTATE <Ctrl+T> opens fuzzy finder with table candidates

Fixes #512

[gemini-code-assist]

Summary of Changes

Hello @apstndb, 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 command-line interface by introducing fuzzy table completion for the MUTATE statement. This improvement allows users to more efficiently select tables when constructing MUTATE commands, streamlining the interaction and reducing potential errors by providing intelligent suggestions.

Highlights

• Fuzzy Table Completion for MUTATE: Implemented fuzzy table completion for the MUTATE statement, allowing users to trigger fuzzy table selection with MUTATE <Ctrl+T>.
• Statement Definition Update: Modified client_side_statement_def.go to include a Completion field with fuzzyCompleteTable for the MUTATE statement definition.
• Test Coverage: Added new test cases in fuzzy_finder_test.go to validate MUTATE table completion, covering scenarios with trailing spaces and partial table names.

Changelog

• internal/mycli/client_side_statement_def.go
  • Added a Completion field to the MUTATE statement definition.
  • Configured fuzzyCompleteTable for MUTATE statements using a regular expression to match the prefix pattern.
• internal/mycli/fuzzy_finder_test.go
  • Introduced new test cases for MUTATE statements to verify fuzzy table completion.
  • Included tests for MUTATE with a trailing space and MUTATE with a partial table name.

Activity

• The author confirmed that make check passes.
• Manual testing was completed, verifying that MUTATE <Ctrl+T> correctly opens the fuzzy finder with table candidates.
• The pull request addresses issue Fuzzy completion: MUTATE <table> statement #512.

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

[github-actions]

Code Metrics Report

📊 View detailed coverage report (available for 7 days)

	main (3b1195d)	#515 (4d7c1b2)	+/-
Coverage	68.2%	68.2%	0.0%
Code to Test Ratio	1:1.2	1:1.2	+0.0
Test Execution Time	2m9s	1m7s	-1m2s

Details

  |                     | main (3b1195d) | #515 (4d7c1b2) |  +/-  |
  |---------------------|----------------|----------------|-------|
  | Coverage            |          68.2% |          68.2% |  0.0% |
  |   Files             |             55 |             55 |     0 |
  |   Lines             |           5912 |           5912 |     0 |
  |   Covered           |           4036 |           4036 |     0 |
+ | Code to Test Ratio  |          1:1.2 |          1:1.2 |  +0.0 |
  |   Code              |          13570 |          13574 |    +4 |
+ |   Test              |          16914 |          16928 |   +14 |
+ | Test Execution Time |           2m9s |           1m7s | -1m2s |

Code coverage of files in pull request scope (79.9% → 79.9%)

Files	Coverage	+/-	Status
internal/mycli/client_side_statement_def.go	79.9%	0.0%	modified

---

Reported by octocov

[gemini-code-assist]

Code Review

The pull request successfully adds fuzzy table completion for the MUTATE statement, which is a valuable enhancement for user productivity. The implementation follows the existing patterns in the codebase and includes appropriate test cases. The previously identified high-severity issue regarding the MUTATE statement's main regex pattern has been re-evaluated against repository rules and found to be acceptable, as the pattern's purpose is to trigger completion, not to fully parse complex identifiers like quoted or spaced names (Rule 5).