fix: fix register selection position

[MinCrohn]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @MinCrohn, 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 addresses a bug related to the selection position within the Patchmap component by refining its state management initialization. The changes ensure that the SelectionState is correctly registered and the overall StateManager is reset when the Patchmap instance is created. This refactoring aims to provide a more robust and predictable handling of selections, preventing potential issues with their initial positioning or behavior.

Highlights

• Refactored Selection State Registration: The registration of the 'selection' state, which manages the position and behavior of selections, has been relocated from the 'draw' method to the 'Patchmap' constructor. This change ensures that the selection state is initialized and registered precisely once when the 'Patchmap' component is created, rather than potentially being re-registered on subsequent draw calls.
• Added State Manager Reset on Initialization: A new call to 'this.stateManager.resetState()' has been introduced within the 'Patchmap' constructor. This addition ensures that the state manager is explicitly reset to a clean slate upon the initialization of the 'Patchmap' component, which is crucial for preventing stale or incorrect state from previous operations and ensuring accurate selection positioning from the start.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 correctly refactors the state registration by moving it from the draw method to init, ensuring it runs only once. However, it introduces a critical issue by calling this.stateManager.resetState() in the constructor before the state manager is initialized in init(). This will lead to a runtime error. I have provided a comment on how to resolve this.