Add correct id to canvas element so engine recognises it

[stmio]

The <canvas> element inside <astro-particles> does not have any id, so the tsParticles engine does not detect it and creates a second one. This means that the canvas within the astro component is not configured (e.g. with fullScreen), and can push content down.

PR adds the correct id to the canvas so a second is not created by the engine.

[coderabbitai]

Walkthrough

A single change was made to the Particles.astro component, adding an id attribute to the <canvas> element. The id value is set from the id prop, aligning it with the data-id attribute on the parent <astro-particles> element. No changes were made to exports or public APIs.

Changes

File(s)	Change Summary
components/astro/src/Particles.astro	Added id attribute to <canvas> using the id prop value.

Estimated code review effort

1 (~2 minutes)

Poem

Upon the canvas, IDs now reside,
A tag for each particle, no longer to hide.
With props passed along, all tidy and neat,
Our code hops forward, nimble and fleet.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9e4752a and c3acf8c.

📒 Files selected for processing (1)

• components/astro/src/Particles.astro (1 hunks)

🔇 Additional comments (1)

components/astro/src/Particles.astro (1)

16-16: LGTM! This change correctly fixes the tsParticles canvas detection issue.

Adding the id attribute to the canvas element ensures that the tsParticles engine can properly identify and use the existing canvas instead of creating a duplicate. This aligns perfectly with how the engine is initialized using this.dataset.id in the script section (lines 38, 40), which corresponds to the data-id attribute on the parent element.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.