fix: support elements option in canvas event

[MinCrohn]

closed: #151

[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 enhances the canvas event system by introducing an "elements" option, providing a more direct way to attach event listeners to specific objects. This change improves flexibility in event management, allowing events to be bound either through a declarative path or by directly referencing elements, and includes new tests to validate the updated behavior.

Highlights

• New 'elements' option for canvas events: Introduced an optional "elements" property in the "addEvent" function, allowing direct specification of target elements for event listeners, complementing the existing "path" selector.
• Flexible event target selection: The event system now intelligently determines event targets, prioritizing explicitly provided "elements" over "path" selectors when both are present, or using "path" if "elements" are not provided.
• Refactored event object retrieval: A new helper function, "getEventObjects", was added to centralize the logic for retrieving target objects for events, supporting both "elements" and "path" based selection.
• Comprehensive test coverage: A new test file, "src/utils/event/canvas.test.js", has been added to ensure the correct functionality and integration of the new "elements" option and related event handling logic.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 adds support for an elements option in canvas events, allowing events to be attached to specific element objects directly, in addition to using a path selector. The changes are well-structured, introducing a new getEventObjects helper and adding comprehensive tests for the new functionality. My review includes a couple of suggestions to improve type safety by using more specific Zod schemas instead of z.unknown(), and a refactoring suggestion to make the new helper function more concise.