• src/blocks/accommodation-related-tour/index.js (11)
• src/blocks/review-related-accommodation/index.js (6)
• src/blocks/review-related-destination/index.js (6)
• src/blocks/review-related-tour/index.js (5)
• src/blocks/tour-related-accommodation/index.js (6)
• src/blocks/tour-related-destination/index.js (6)

• build/blocks/accommodation-related-tour/block.json
• build/blocks/review-related-accommodation/block.json
• build/blocks/review-related-destination/block.json
• build/blocks/review-related-tour/block.json
• build/blocks/tour-related-accommodation/block.json
• build/blocks/tour-related-destination/block.json
• src/blocks/accommodation-related-tour/block.json
• src/blocks/review-related-accommodation/block.json
• src/blocks/review-related-destination/block.json
• src/blocks/review-related-tour/block.json
• src/blocks/tour-related-accommodation/block.json
• src/blocks/tour-related-destination/block.json

• src/blocks/accommodation-related-tour/index.js (diff tokens exceeds limit)
• src/blocks/tour-related-accommodation/index.js (nothing obtained from openai)
• src/blocks/review-related-destination/index.js (nothing obtained from openai)
• src/blocks/tour-related-destination/index.js (nothing obtained from openai)
• src/blocks/review-related-accommodation/index.js (nothing obtained from openai)
• src/blocks/review-related-tour/index.js (nothing obtained from openai)

• src/blocks/tour-related-destination/index.js (no response)
• src/blocks/accommodation-related-tour/index.js (no response)
• src/blocks/review-related-accommodation/index.js (no response)
• src/blocks/review-related-tour/index.js (no response)
• src/blocks/review-related-destination/index.js (no response)
• src/blocks/tour-related-accommodation/index.js (no response)

• Review: 0
• LGTM: 0

Chat with CodeRabbit Bot (@coderabbitai)

• Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
• Invite the bot into a review comment chain by tagging @coderabbitai in a reply.

Code suggestions

• The bot may make code suggestions, but please review them carefully before committing since the line number ranges may be misaligned.
• You can edit the comment made by the bot and manually tweak the suggestion if it is slightly off.

Pausing incremental reviews

• Add @coderabbitai: ignore anywhere in the PR description to pause further reviews from the bot.

src/blocks/tour-related-destination/block.json (1)

18-22: Standardise example metadata name. The example metadata still carries the old plural label, so previews will surface wording that no longer matches the block title. Please align the example name with the new singular title to keep localisation tidy.

-        "name": "Related Tours - Destinations"
+        "name": "Related Tours - Destination"

src/blocks/review-related-destination/index.js (2)

1-11: Add @SInCE tags to JSDoc blocks. Both JSDoc headers are missing the required @SInCE annotation, which our coding guidelines mandate for new block code. Please add the correct version reference to each block comment.

---

118-118: Finish the inline comment with a period. The line comment should end with a full stop to satisfy the documented commenting rules.

src/blocks/review-related-accommodation/index.js (2)

1-11: Add @SInCE tags to JSDoc blocks. Please include the mandated @SInCE annotation in both JSDoc headers so the documentation aligns with our standards.

---

117-117: Add the missing full stop to the comment. The inline comment should conclude with a period to stay consistent with our commenting rules.

src/blocks/review-related-destination/block.json (1)

9-9: Correct the description grammar. The description should read “Displays …” to remain grammatical and consistent with the other blocks’ copy.

-  "description": "Display reviews related to destination posts.",
+  "description": "Displays reviews related to destination posts.",

src/blocks/accommodation-related-tour/index.js (1)

114-208: Align the example content with accommodations.

The inserter example still speaks about tours (“Related tours”, tour itineraries). Because this block surfaces accommodations, the preview should showcase accommodation-focused copy to avoid confusing editors. Consider updating the labels and sample cards, e.g.:

-               metadata: {
-                   name: __('Related tours', 'tour-operator'),
+               metadata: {
+                   name: __('Related accommodations', 'tour-operator'),
...
-                               content: __('Related tours', 'tour-operator'),
+                               content: __('Related accommodations', 'tour-operator'),
...
-                                       ['core/heading', { content: __('African Safari Adventure', 'tour-operator'), level: 3 }],
-                                       ['core/paragraph', { content: __("Embark on an unforgettable 7-day safari experience through Kenya's most spectacular wildlife reserves.", 'tour-operator') }],
+                                       ['core/heading', { content: __('Savanna View Lodge', 'tour-operator'), level: 3 }],
+                                       ['core/paragraph', { content: __('Experience luxury suites overlooking the Mara savanna with guided wildlife excursions included.', 'tour-operator') }],

…and update the remaining cards similarly to describe accommodations.

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

src/blocks/review-related-tour/index.js (1)

1-3: Add @since metadata and tidy up comment punctuation.

Both JSDoc blocks at the top of the file and above registerReviewRelatedTourVariation are missing the required @since tag, and the summary lines (as well as the inline comment at Line 266) do not end with a full stop. Project guidelines call for every JSDoc to include @since <next-plugin-version> and for line comments to end with a period. Please add an appropriate @since tag to both docblocks and update the comment text to end in full stops. As per coding guidelines.

Also applies to: 8-10, 266-270

src/blocks/tour-related-destination/index.js (1)

1-10: Add @since tags to both JSDoc comments.

The file‑level and function‑level docblocks are still missing the required @since annotation. Please add an appropriate version (for example @since 2.1.0, or whatever version this will ship in) to both comments to comply with the project’s JSDoc / WordPress documentation rules.

src/blocks/review-related-tour/index.js (1)

4-6: Consider importing __ from @wordpress/i18n instead of using the global.

Using const { __ } = wp.i18n; relies on the global wp object; modern WordPress block code typically imports from @wordpress/i18n and declares wp-i18n as a script dependency instead. If the build setup allows, consider:

-import { registerForPostTypes } from '@utils/conditional-block-registration.js';
-
-const { __ } = wp.i18n;
+import { __ } from '@wordpress/i18n';
+import { registerForPostTypes } from '@utils/conditional-block-registration.js';

to better align with @wordpress/scripts patterns.

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

• src/blocks/accommodation-related-destination/index.js (4)
• src/blocks/review-related-destination/index.js (6)
• src/blocks/tour-related-destination/index.js (5)

• src/blocks/accommodation-related-destination/index.js (diff tokens exceeds limit)
• src/blocks/review-related-destination/index.js (diff tokens exceeds limit)
• src/blocks/tour-related-destination/index.js (diff tokens exceeds limit)

• src/blocks/accommodation-related-destination/index.js (no response)
• src/blocks/review-related-destination/index.js (no response)
• src/blocks/tour-related-destination/index.js (no response)

• Review: 0
• LGTM: 0

Chat with CodeRabbit Bot (@coderabbitai)

• Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
• Invite the bot into a review comment chain by tagging @coderabbitai in a reply.

Code suggestions

• The bot may make code suggestions, but please review them carefully before committing since the line number ranges may be misaligned.
• You can edit the comment made by the bot and manually tweak the suggestion if it is slightly off.

Pausing incremental reviews

• Add @coderabbitai: ignore anywhere in the PR description to pause further reviews from the bot.

src/blocks/tour-related-destination/index.js (3)

376-378: supports.renaming on a variation will not actually disable renaming.

The supports: { renaming: false } on this registerBlockVariation call does not affect the underlying core/group block’s supports, so it will not prevent renaming in the editor. Renaming behaviour can currently only be controlled at the block type level (e.g. via supports.renaming in block.json), not per variation.

If you do not plan to register a dedicated block type with supports.renaming = false, it is less confusing to remove this property:

-        supports: {
-            renaming: false,
-        },

---

389-389: Terminate the inline comment with a full stop.

The line comment should end with a period to comply with the project’s commenting convention:

-// Register conditionally for destination post types and destination templates
+// Register conditionally for destination post types and destination templates.

---

1-10: Add @SInCE tags and full stops to the JSDoc headers.

Both JSDoc-style docblocks are missing the required @since annotation, and the summary lines should end with a full stop to match the project’s documentation rules. Consider something along these lines (adjust the version to the actual release you are targeting):

 /**
- * Register Tour Related Destination block variation
+ * Register Tour Related Destination block variation.
+ *
+ * @since 2.1.0
  */
 
 /**
- * Register the tours related to destination block variation
+ * Register the tours related to destination block variation.
+ *
+ * @since 2.1.0
  */

src/blocks/review-related-destination/index.js (2)

1-3: Add required @since tags and finish sentences in JSDoc.

Both JSDoc-style comments at the top of the file and above registerReviewRelatedDestinationVariation() are missing the required @since tag, and their description lines don’t end with a full stop. Please add an appropriate @since version (the next plugin release, e.g. @since 2.1.0) to each block and end the description lines with a period to match the project’s documentation standard.

Also applies to: 8-10

---

254-263: supports.renaming on the variation is ignored by the Block Variations API.

The supports: { renaming: false } property on the variation object won’t have any effect: wp.blocks.registerBlockVariation() only recognises documented variation keys (name, title, icon, keywords, attributes, innerBlocks, example, scope, isDefault, isActive, etc.), and supports isn’t among them. (developer.wordpress.org)

If preventing renaming is important, you’ll need to enforce it at the block type level (e.g. via block.json or a block_type_metadata filter) rather than on the variation object. In this variation, I’d suggest removing the supports block to avoid confusion and duplicating that logic where it actually applies.

Does the WordPress Block Variations API support a `supports` key (e.g. `supports.renaming`) on variation objects passed to `wp.blocks.registerBlockVariation`, or is `supports` limited to the block type registration (`registerBlockType` / `block.json`)?

src/blocks/accommodation-related-destination/index.js (2)

51-56: Consider aligning heading text capitalisation for consistency.

The heading content in the live variation is Related accommodations (lowercase “a”), while the example heading uses Related Accommodations (capital “A”). For a slightly more polished editor experience, you might want to standardise these to the same casing in both places.

Also applies to: 114-137

---

111-113: Remove the unused supports block from the variation definition.

The supports property on a block variation definition is not used by the Block Variations API. The supports property belongs only to block type registration (registerBlockType / block.json), and registerBlockVariation does not apply or override block supports. Dropping the supports block at lines 111-113 will prevent implying behaviour that doesn't occur.

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

• src/blocks/accommodation-related-destination/index.js (4)

• src/blocks/accommodation-related-destination/index.js (diff tokens exceeds limit)

• src/blocks/accommodation-related-destination/index.js (no response)

• Review: 0
• LGTM: 0

Chat with CodeRabbit Bot (@coderabbitai)

• Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
• Invite the bot into a review comment chain by tagging @coderabbitai in a reply.

Code suggestions

• The bot may make code suggestions, but please review them carefully before committing since the line number ranges may be misaligned.
• You can edit the comment made by the bot and manually tweak the suggestion if it is slightly off.

Pausing incremental reviews

• Add @coderabbitai: ignore anywhere in the PR description to pause further reviews from the bot.