refactor(stores): convert CommandTreeProvider to Store-based architecture

[KubrickCode]

Migrate from EventBus/ConfigManager pattern to direct Zustand Store subscription

• Remove configManager, configReader, eventBus dependencies
• Remove ButtonSetManager dependency (Store manages active set buttons)
• Use store.subscribe for button change detection and auto-refresh
• Add error handling and memory leak prevention in dispose

fix #194

[gemini-code-assist]

Summary of Changes

Hello @KubrickCode, 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 significantly refactors the CommandTreeProvider to adopt a modern, store-based state management approach. By integrating with a Zustand store, the provider can now reactively update its displayed commands, simplifying its internal logic and reducing coupling with older event-driven and manager-based systems. This change aims to improve maintainability, predictability, and performance of the command tree view.

Highlights

• Architecture Refactor: The CommandTreeProvider has been refactored to utilize a Zustand-based store architecture, moving away from the EventBus/ConfigManager pattern.
• Dependency Removal: Removed direct dependencies on ConfigManager, ConfigReader, EventBus, and ButtonSetManager from CommandTreeProvider.
• Store-based Reactivity: The CommandTreeProvider now subscribes directly to the application store for button changes, triggering auto-refresh of the tree view.
• Improved Resource Management: Enhanced the dispose method to prevent memory leaks by properly unsubscribing from the store and including error handling for refresh operations.
• Test Suite Update: The test suite for CommandTreeProvider has been updated to reflect the new store-based implementation, including tests for store subscription and disposal.

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

[KubrickCode]

/gemini review

[gemini-code-assist]

Code Review

This pull request is an excellent refactoring of the CommandTreeProvider to use a Zustand store-based architecture. The changes effectively decouple the provider from ConfigManager and EventBus, centralizing state management and simplifying the data flow. The new implementation is clean, includes proper error handling in subscriptions, and ensures there are no memory leaks by correctly handling disposal. The accompanying test suite has been thoroughly updated to reflect these changes, with well-structured and comprehensive tests that validate the new behavior. I've found one minor style guide violation regarding class member ordering, which I've detailed in a comment. Overall, this is a high-quality contribution that significantly improves the codebase's architecture and maintainability.

[KubrickCode]

🎉 This PR is included in version 0.10.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀