fix(#55): update DruxtEntity component key

[Decipher]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Incorrect key can be the cause for hydration leaks.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

Screenshots/Media:

Summary by CodeRabbit

• Bug Fixes

  • Resolved an issue in the "druxt-layout-paragraphs" component (issue Incorrect key in DruxtFieldLayoutParagraphs #55) to improve data handling and rendering.

• Refactor

  • Updated the rendering logic in DruxtFieldLayoutParagraphs to use paragraph.id instead of paragraph.uuid for better performance and consistency.

[changeset-bot]

🦋 Changeset detected

Latest commit: cf6b743

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
druxt-layout-paragraphs	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

This update focuses on a targeted fix for the druxt-layout-paragraphs component, addressing issue #55. The primary changes involve modifying the key and prop bindings of paragraphs within the DruxtFieldLayoutParagraphs.vue component to use paragraph.id instead of paragraph.uuid. This enhancement aims to standardize identifier usage, potentially boosting Vue's reactivity performance and ensuring consistency in data handling and rendering within the Druxt framework.

Changes

File	Change Summary
.changeset/itchy-knives-deliver.md	Added a summary detailing the enhancement to the DruxtEntity key within the LayoutParagraphs component addressing issue #55.
src/components/DruxtFieldLayoutParagraphs.vue	Updated v-for key and uuid prop binding from paragraph.uuid to paragraph.id, ensuring consistent identifier usage.

Poem

In the realm of Druxt's delight,
Paragraphs find their proper flight.
id takes the place of uuid,
Performance soars, reactions glide.
A fix so neat, a patch so bright,
Our code now dances, just right.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between fc80a46 and cf6b743.

Files selected for processing (2)

• .changeset/itchy-knives-deliver.md (1 hunks)
• src/components/DruxtFieldLayoutParagraphs.vue (1 hunks)

Additional comments not posted (2)

.changeset/itchy-knives-deliver.md (1)

1-5: LGTM! The changeset is correctly formatted and the description is accurate.

The changeset file provides the necessary metadata and a clear description of the fix.

src/components/DruxtFieldLayoutParagraphs.vue (1)

Line range hint 5-9:
LGTM! The key and prop bindings are correctly updated.

The changes to use paragraph.id instead of paragraph.uuid are correctly implemented and align with the PR objectives to fix the hydration leak issue.