fix: resolve link rendering error based on Relations rendering order

[MinCrohn]

This resolves an issue where links would not render correctly if the relations object was rendered before its link targets.

[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 where graphical links (referred to as 'relations') might not render correctly, or at all, if their target elements were not yet drawn. The changes ensure that these relations are properly displayed by controlling their rendering order and visual layering, thereby resolving the reported link rendering errors.

Highlights

• Rendering Order Correction: I've introduced an explicit refresh mechanism for 'relations' elements in src/patchmap.js after the initial drawing phase. This ensures that all link targets are rendered before the relations themselves are processed, resolving issues where links might not appear due to an incorrect rendering sequence.
• Visual Layering Enhancement: In src/utils/convert.js, I've assigned a higher zIndex (20) to 'relations' elements, ensuring they are rendered on top of other graphical components (which are now consistently assigned zIndex 10). This improves visibility and prevents links from being obscured by other elements.

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 is currently in preview and 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 to provide feedback.

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 effectively resolves a link rendering issue caused by the processing order of relation elements and their targets. The solution, which involves forcing a post-draw update for relations and adjusting their zIndex, is robust and well-implemented. My feedback includes a couple of suggestions to enhance code maintainability by replacing magic numbers with named constants and adding a clarifying comment to the core fix.