• src/blocks/best-time-to-visit/index.js (1)
• src/blocks/facts-country-wrapper/index.js (1)
• src/blocks/facts-regions-wrapper/index.js (1)
• src/blocks/safety/index.js (1)
• src/blocks/visa/index.js (1)

• build/blocks/best-time-to-visit/block.json
• build/blocks/facts-country-wrapper/block.json
• build/blocks/facts-regions-wrapper/block.json
• build/blocks/safety/block.json
• build/blocks/visa/block.json
• src/blocks/best-time-to-visit/block.json
• src/blocks/facts-country-wrapper/block.json
• src/blocks/facts-regions-wrapper/block.json
• src/blocks/safety/block.json
• src/blocks/visa/block.json

• src/blocks/safety/index.js (diff tokens exceeds limit)
• src/blocks/best-time-to-visit/index.js (nothing obtained from openai)
• src/blocks/facts-regions-wrapper/index.js (nothing obtained from openai)
• src/blocks/facts-country-wrapper/index.js (nothing obtained from openai)
• src/blocks/visa/index.js (nothing obtained from openai)

• src/blocks/safety/index.js (no response)
• src/blocks/facts-country-wrapper/index.js (no response)
• src/blocks/facts-regions-wrapper/index.js (no response)
• src/blocks/best-time-to-visit/index.js (no response)
• src/blocks/visa/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/facts-regions-wrapper/block.json (5)

4-4: Use the "lsx-to" namespace for the block name.
As per guidelines, blocks under src should use the lsx-to namespace. If you must keep the old name for back-compat, consider aliasing via a JS deprecation path and registering the new name alongside it. As per coding guidelines

-  "name": "lsx-tour-operator/facts-regions-wrapper",
+  "name": "lsx-to/facts-regions-wrapper",

---

15-15: Icon should use the central icon system.
PR objective says to replace hardcoded icons with the central lsx-tour-operator/icons. Keep a generic fallback here if needed, but override the icon via editorScript (index.js) to pull from the central icons registry. As per coding guidelines

Example override in index.js (no block.json change required):

registerBlockType( metadata.name, {
  ...metadata,
  icon: lsxTOIcons?.regions || metadata.icon,
} );

---

19-35: Clean up supports: remove non-standard key and tighten accessibility supports.
“renaming” isn’t a valid supports flag. Consider adding anchor and disabling raw HTML editing. As per coding guidelines

   "supports": {
-    "renaming": false,
+    "anchor": true,
+    "html": false,
     "color": {
       "background": true,
       "text": true,
       "link": true
     },
     "spacing": {
       "padding": true,
       "margin": true,
       "blockGap": true
     },
     "typography": {
       "fontSize": true,
       "lineHeight": true
     }
   },

Note: keep blockGap only if this wrapper actually contains InnerBlocks or nested content.

---

36-43: Enhance example for inserter preview and accessibility.
Consider adding a minimal innerBlocks preview (if this wrapper contains InnerBlocks) and clarify accessible usage in description (e.g., heading levels, list semantics). As per coding guidelines

Example augmentation:

   "example": {
     "attributes": {
       "metadata": {
         "name": "Regions list"
       },
       "className": "facts-regions-query-wrapper"
-    }
+    },
+    "innerBlocks": [
+      { "name": "core/list", "attributes": { "ordered": false }, "innerBlocks": [
+        { "name": "core/list-item", "attributes": { "content": "Region A" } },
+        { "name": "core/list-item", "attributes": { "content": "Region B" } }
+      ] }
+    ]
   },

Also consider adding "usesInnerBlocks": true if applicable.

---

6-14: Description and keywords look good, but add editor a11y guidance.
Include brief guidance (e.g., “Use appropriate heading hierarchy; lists should reflect actual regions; avoid using this block for arbitrary content”). As per coding guidelines

src/blocks/safety/block.json (6)

19-35: Harden supports: disable HTML editing and enable anchors.

Prevents raw HTML edits and allows anchor links. Non-breaking.

   "supports": {
     "renaming": false,
+    "html": false,
+    "anchor": true,
     "color": {
       "background": true,
       "text": true,
       "link": true
     },

---

17-19: Restrict inserter to destination contexts via postTypes.

Add postTypes to align with conditional registration goals and hide the block outside allowed editors. Confirm CPT slugs (e.g. destination, country, region).

Example:

"postTypes": ["destination", "country", "region"]

---

6-14: Augment description with editor a11y guidance.

Add a short note (e.g. avoid colour-only cues; provide clear headings/ARIA for expandable sections).

---

36-43: Enrich example for better inserter preview.

Include innerBlocks (e.g. an icon + paragraph) so users see a realistic preview.

Example:

"example": {
  "attributes": {
    "metadata": { "name": "Safety" },
    "className": "lsx-safety-wrapper"
  },
  "innerBlocks": [
    { "name": "core/paragraph", "attributes": { "content": "Always follow local guidance and check travel advisories." } }
  ]
}

---

15-15: Align icon with the central icons system.

"shield" is a Dashicon slug. If the project uses a central icons package, ensure index.js sets the icon from that source or update block.json to reference it.

---

17-17: Confirm the non-standard "version" field.

Block schema may ignore unknown fields. If unused by tooling, consider removing to reduce noise; else document its purpose.

src/blocks/visa/block.json (3)

6-6: Enhance description with accessibility guidance.

Add editor-facing a11y guidance (e.g., icons are decorative; ensure headings/text convey meaning for screen readers).

As per coding guidelines

---

16-20: Add post type gating in manifest (if keeping this as a real block).

If this block.json is intended to define a block (with future server-side registration), include postTypes to limit insertion to Destinations. Note: this has no effect on a client-only variation.

   "category": "lsx-tour-operator",
+  "postTypes": [ "destination" ],
   "version": "1.0.0",

As per coding guidelines

---

19-43: Clarify intent: block vs variation.

At runtime you only register a variation of core/group. Without server-side register_block_type, this block.json’s supports, version, example, etc. will not affect the editor. Either:

• Register a real block server-side (preferred for manifests), or
• Treat this as variation-only and remove/reduce block.json to avoid confusion.

As per coding guidelines

src/blocks/facts-country-wrapper/block.json (3)

6-6: Add a11y detail in description.

Include guidance for screen reader users and explain icon semantics.

As per coding guidelines

---

16-20: Limit to Destination post type in manifest (if this remains a block).

Add postTypes to constrain usage. Has effect only if block is actually registered server-side.

   "category": "lsx-tour-operator",
+  "postTypes": [ "destination" ],
   "version": "1.0.0",

As per coding guidelines

---

19-43: Manifest vs variation mismatch.

Current runtime registers a core/group variation. If there is no PHP register_block_type, the manifest’s supports and example won’t apply. Decide between promoting this to a real block (server-side registration) or keeping it as variation-only and simplifying the manifest.

As per coding guidelines

src/blocks/facts-regions-wrapper/index.js (4)

18-22: Remove unsupported variation properties and stabilise isActive.

• category is not a supported property for block variations and has no effect.
• isActive comparing translated metadata.name is brittle across locales. Prefer a stable marker like className.

         wp.blocks.registerBlockVariation('core/group', {
             name: 'lsx-tour-operator/facts-regions-wrapper',
             title: __('Regions list', 'tour-operator'),
-            icon: 'admin-site-alt',
-            category: 'lsx-tour-operator',
-            isActive: (blockAttributes, variationAttributes) => {
-                return blockAttributes.metadata?.name === variationAttributes.metadata?.name;
-            },
+            icon: 'admin-site-alt',
+            isActive: (blockAttributes, variationAttributes) => {
+                return blockAttributes.className === variationAttributes.className;
+            },

As per coding guidelines

---

87-89: Drop supports from variation; it is ignored.

supports is for block types, not variations. Safe to remove.

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

As per coding guidelines

---

126-166: Replace polling with wp.data.subscribe for robust gating.

Polling every 100ms for up to 5s is noisy and can miss late readiness. Use subscribe and unsubscribe once registered.

-wp.domReady(() => {
-    const { select } = wp.data;
-    // Define supported post types
-    const supportedPostTypes = ['destination'];
-    let registered = false;
-    // Check if current post type is supported
-    const checkAndRegister = () => {
-        if (registered) {
-            return true;
-        }
-        const postType = select('core/editor')?.getCurrentPostType();
-        const postSlug = select('core/editor')?.getEditedPostSlug();
-        if (!postType || !postSlug) {
-            return false;
-        }
-        if (supportedPostTypes.includes(postType) || ((postType === 'wp_template' || postType === 'wp_template_part') && (postSlug.includes('destination') || postSlug.includes('country') || postSlug.includes('region')))) {
-            registerFactsRegionsWrapperVariation();
-            registered = true;
-        }
-        return registered;
-    };
-    // Try immediate registration
-    if (!checkAndRegister()) {
-        // If not ready, check periodically
-        const interval = setInterval(() => {
-            if (checkAndRegister()) {
-                clearInterval(interval);
-            }
-        }, 100);
-        // Clean up after 5 seconds to prevent infinite checking
-        setTimeout(() => clearInterval(interval), 5000);
-    }
-});
+wp.domReady(() => {
+    const { select, subscribe } = wp.data;
+    const supportedPostTypes = ['destination'];
+    let unsub;
+    const timeout = setTimeout(() => { if (unsub) { unsub(); } }, 5000);
+    unsub = subscribe(() => {
+        const postType = select('core/editor')?.getCurrentPostType();
+        const postSlug = select('core/editor')?.getEditedPostSlug();
+        if (!postType || !postSlug) {
+            return;
+        }
+        if (
+            supportedPostTypes.includes(postType) ||
+            ((postType === 'wp_template' || postType === 'wp_template_part') &&
+             (postSlug.includes('destination') || postSlug.includes('country') || postSlug.includes('region')))
+        ) {
+            if (registerFactsRegionsWrapperVariation()) {
+                if (unsub) { unsub(); }
+                clearTimeout(timeout);
+            }
+        }
+    });
+});

As per coding guidelines

---

129-134: Nit: end line comments with periods.

Inline comments should end with a period per guidelines.

As per coding guidelines

Also applies to: 154-165

src/blocks/best-time-to-visit/block.json (3)

6-6: Add accessibility note in description.

Include brief guidance for assistive tech (e.g., ensure month labels are text; icons are decorative).

As per coding guidelines

---

17-20: Add postTypes if treating this as a block.

Limit inserter availability to Destinations at manifest level. Has effect only with server-side registration.

   "category": "lsx-tour-operator",
+  "postTypes": [ "destination" ],
   "version": "1.0.0",

As per coding guidelines

---

19-44: Manifest likely unused for a variation-only implementation.

Since runtime registers a core/group variation, this manifest’s supports/example will not apply unless you also register a block type server-side. Please align intent.

As per coding guidelines

src/blocks/best-time-to-visit/index.js (4)

18-22: Remove unsupported category and stabilise isActive.

• category is ignored for variations.
• Comparing translated metadata.name risks false negatives when locale changes. Use a stable className.

         wp.blocks.registerBlockVariation('core/group', {
             name: 'lsx-tour-operator/best-time-to-visit',
             title: __('Best time to visit', 'tour-operator'),
-            icon: 'calendar-alt',
-            category: 'lsx-tour-operator',
-            isActive: (blockAttributes, variationAttributes) => {
-                return blockAttributes.metadata?.name === variationAttributes.metadata?.name;
-            },
+            icon: 'calendar-alt',
+            isActive: (blockAttributes, variationAttributes) => {
+                return blockAttributes.className === variationAttributes.className;
+            },

As per coding guidelines

---

82-84: Remove supports from the variation.

supports only applies to block types; it is ignored here.

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

As per coding guidelines

---

121-161: Prefer wp.data.subscribe to polling for registration gating.

Replace setInterval + timeout with a one-shot subscription that cleans up. Less churn, more reliable.

-wp.domReady(() => {
-    const { select } = wp.data;
-    // Define supported post types
-    const supportedPostTypes = ['destination'];
-    let registered = false;
-    // Check if current post type is supported
-    const checkAndRegister = () => {
-        if (registered) {
-            return true;
-        }
-        const postType = select('core/editor')?.getCurrentPostType();
-        const postSlug = select('core/editor')?.getEditedPostSlug();
-        if (!postType || !postSlug) {
-            return false;
-        }
-        if (supportedPostTypes.includes(postType) || ((postType === 'wp_template' || postType === 'wp_template_part') && (postSlug.includes('destination') || postSlug.includes('country') || postSlug.includes('region')))) {
-            registerBestTimeToVisitVariation();
-            registered = true;
-        }
-        return registered;
-    };
-    // Try immediate registration
-    if (!checkAndRegister()) {
-        // If not ready, check periodically
-        const interval = setInterval(() => {
-            if (checkAndRegister()) {
-                clearInterval(interval);
-            }
-        }, 100);
-        // Clean up after 5 seconds to prevent infinite checking
-        setTimeout(() => clearInterval(interval), 5000);
-    }
-});
+wp.domReady(() => {
+    const { select, subscribe } = wp.data;
+    const supportedPostTypes = ['destination'];
+    let unsub;
+    const timeout = setTimeout(() => { if (unsub) { unsub(); } }, 5000);
+    unsub = subscribe(() => {
+        const postType = select('core/editor')?.getCurrentPostType();
+        const postSlug = select('core/editor')?.getEditedPostSlug();
+        if (!postType || !postSlug) {
+            return;
+        }
+        if (
+            supportedPostTypes.includes(postType) ||
+            ((postType === 'wp_template' || postType === 'wp_template_part') &&
+             (postSlug.includes('destination') || postSlug.includes('country') || postSlug.includes('region')))
+        ) {
+            if (registerBestTimeToVisitVariation()) {
+                if (unsub) { unsub(); }
+                clearTimeout(timeout);
+            }
+        }
+    });
+});

As per coding guidelines

---

124-129: Minor: end comments with periods.

Inline comments should end with a period to match guidelines.

As per coding guidelines

Also applies to: 149-160

src/blocks/visa/index.js (4)

17-20: Remove non-variation props; consider centralised icon source.

• category is not a supported variation option; remove it.
• Keep icon, but prefer using your central icons module if available for consistency.

As per coding guidelines.

-            icon: 'id-alt',
-            category: 'lsx-tour-operator',
+            icon: 'id-alt',

If the icons package exposes an inserter icon, import and use it for the icon prop. Please confirm the module’s API before changing.

---

96-99: Drop unsupported supports on variation.

supports.renaming is a block-level setting, not recognised on variations; it has no effect here.

As per coding guidelines.

-            supports: {
-                renaming: false,
-            },
+            // Removed unsupported variation property: supports.

---

47-52: Use a semantic heading instead of paragraph+strong.

For accessibility and consistency with your example, use core/heading (with level) instead of a paragraph with bold text.

As per coding guidelines.

-                                [
-                                    'core/paragraph',
-                                    {
-                                        align: 'center',
-                                        content: `<strong>${__('Visa', 'tour-operator')}</strong>`,
-                                    },
-                                ],
+                                [
+                                    'core/heading',
+                                    {
+                                        textAlign: 'center',
+                                        level: 3,
+                                        content: __('Visa', 'tour-operator'),
+                                    },
+                                ],

---

138-174: Prefer wp.data.subscribe over polling; add full stop to comments.

• Replace setInterval/timeout polling with wp.data.subscribe to react to editor readiness/state changes reliably.
• Also, end single-line comments with a period to meet the style guide.

As per coding guidelines.

Example approach:

const unsubscribe = wp.data.subscribe(() => {
    const postType = select('core/editor')?.getCurrentPostType();
    const postSlug = select('core/editor')?.getEditedPostSlug();
    if (postType && postSlug && !registered &&
        (supportedPostTypes.includes(postType) ||
         ((postType === 'wp_template' || postType === 'wp_template_part') &&
          (postSlug.includes('destination') || postSlug.includes('country') || postSlug.includes('region'))))) {
        if (registerVisaVariation()) {
            registered = true;
            unsubscribe();
        }
    }
});

src/blocks/safety/index.js (4)

17-20: Remove category on variation; consider central icon source.

• category isn’t a supported variation prop; remove it.
• Prefer a centralised icon import for icon consistency if available.

As per coding guidelines.

-            icon: 'shield',
-            category: 'lsx-tour-operator',
+            icon: 'shield',

---

96-98: Remove unsupported supports from the variation.

supports.renaming won’t be applied at the variation level.

As per coding guidelines.

-            supports: {
-                renaming: false,
-            },
+            // Removed unsupported variation property: supports.

---

47-52: Use core/heading for the title (semantic).

Replace paragraph+strong with a heading for better a11y.

As per coding guidelines.

-                                [
-                                    'core/paragraph',
-                                    {
-                                        align: 'center',
-                                        content: `<strong>${__('Safety', 'tour-operator')}</strong>`,
-                                    },
-                                ],
+                                [
+                                    'core/heading',
+                                    {
+                                        textAlign: 'center',
+                                        level: 3,
+                                        content: __('Safety', 'tour-operator'),
+                                    },
+                                ],

---

135-176: Switch polling to wp.data.subscribe; end comments with full stops.

• Use a subscribe listener to register when state is ready.
• Ensure inline comments end with a period.

As per coding guidelines.

Example:

const unsubscribe = wp.data.subscribe(() => {
    const postType = select('core/editor')?.getCurrentPostType();
    const postSlug = select('core/editor')?.getEditedPostSlug();
    if (!registeredSafety && postType && postSlug &&
        (supportedPostTypes.includes(postType) ||
        ((postType === 'wp_template' || postType === 'wp_template_part') &&
         (postSlug.includes('destination') || postSlug.includes('country') || postSlug.includes('region'))))) {
        if (registerSafetyVariation()) {
            registeredSafety = true;
            unsubscribe();
        }
    }
});

src/blocks/facts-country-wrapper/index.js (4)

27-31: Standardise class naming with the lsx- prefix.

Other wrappers use the lsx- prefix (e.g., lsx-safety-wrapper). Aligning improves consistency and theming hooks.

As per coding guidelines.

-                className: 'facts-country-query-wrapper',
+                className: 'lsx-facts-country-query-wrapper',

Remember to update the isActive check and any CSS selectors accordingly.

---

19-19: Remove category from the variation.

category is not a recognised variation option.

As per coding guidelines.

-            category: 'lsx-tour-operator',
+            // Removed unsupported variation property: category.

---

87-89: Remove unsupported supports from the variation.

supports.renaming has no effect at the variation level.

As per coding guidelines.

-            supports: {
-                renaming: false,
-            },
+            // Removed unsupported variation property: supports.

---

126-165: Replace polling with subscribe; add full stops to comments.

Use wp.data.subscribe to register deterministically when editor state is ready, and end comments with periods.

As per coding guidelines.

Example:

const unsubscribe = wp.data.subscribe(() => {
    const postType = select('core/editor')?.getCurrentPostType();
    const postSlug = select('core/editor')?.getEditedPostSlug();
    if (!registered && postType && postSlug &&
        (supportedPostTypes.includes(postType) ||
        ((postType === 'wp_template' || postType === 'wp_template_part') &&
         (postSlug.includes('destination') || postSlug.includes('country') || postSlug.includes('region'))))) {
        if (registerFactsCountryWrapperVariation()) {
            registered = true;
            unsubscribe();
        }
    }
});

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

• src/blocks/best-time-to-visit/index.js (1)
• src/blocks/facts-country-wrapper/index.js (1)
• src/blocks/facts-regions-wrapper/index.js (1)
• src/blocks/safety/index.js (1)
• src/blocks/visa/index.js (1)

• src/blocks/safety/index.js (diff tokens exceeds limit)
• src/blocks/best-time-to-visit/index.js (nothing obtained from openai)
• src/blocks/facts-regions-wrapper/index.js (nothing obtained from openai)
• src/blocks/facts-country-wrapper/index.js (nothing obtained from openai)
• src/blocks/visa/index.js (nothing obtained from openai)

• src/blocks/visa/index.js (no response)
• src/blocks/facts-country-wrapper/index.js (no response)
• src/blocks/best-time-to-visit/index.js (no response)
• src/blocks/safety/index.js (no response)
• src/blocks/facts-regions-wrapper/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.

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

• src/blocks/best-time-to-visit/index.js (1)
• src/blocks/facts-country-wrapper/index.js (1)
• src/blocks/facts-regions-wrapper/index.js (1)
• src/blocks/safety/index.js (1)
• src/blocks/visa/index.js (1)

• src/blocks/safety/index.js (diff tokens exceeds limit)
• src/blocks/facts-country-wrapper/index.js (nothing obtained from openai)
• src/blocks/facts-regions-wrapper/index.js (nothing obtained from openai)
• src/blocks/best-time-to-visit/index.js (nothing obtained from openai)
• src/blocks/visa/index.js (nothing obtained from openai)

• src/blocks/best-time-to-visit/index.js (no response)
• src/blocks/facts-country-wrapper/index.js (no response)
• src/blocks/facts-regions-wrapper/index.js (no response)
• src/blocks/safety/index.js (no response)
• src/blocks/visa/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/safety/index.js (1)

134-186: Extract the registration orchestration into a shared utility.

The domReady callback (lines 134-186) duplicates identical registration logic across visa, safety, facts-country-wrapper, and facts-regions-wrapper files.

See the recommendation in src/blocks/visa/index.js at lines 134-184 to extract this pattern into a shared utility function.

src/blocks/facts-country-wrapper/index.js (1)

125-175: Extract the registration orchestration into a shared utility.

The domReady callback (lines 125-175) duplicates identical registration logic across visa, safety, facts-country-wrapper, and facts-regions-wrapper files.

See the recommendation in src/blocks/visa/index.js at lines 134-184 to extract this pattern into a shared utility function.

src/blocks/facts-regions-wrapper/index.js (1)

125-175: Extract the registration orchestration into a shared utility.

The domReady callback (lines 125-175) duplicates identical registration logic across visa, safety, facts-country-wrapper, and facts-regions-wrapper files.

See the recommendation in src/blocks/visa/index.js at lines 134-184 to extract this pattern into a shared utility function.

src/blocks/visa/index.js (2)

13-132: Add JSDoc documentation for the registration function.

The registerVisaVariation function lacks JSDoc comments. All functions should include JSDoc with a description, @return tag, and @since tag.

As per coding guidelines.

Apply this diff to add documentation:

+/**
+ * Registers the Visa block variation for destination post types.
+ *
+ * @since 2.1.0
+ * @return {boolean} True if registration succeeded, false otherwise.
+ */
 function registerVisaVariation() {

---

134-184: Extract the registration orchestration into a shared utility.

The domReady callback (lines 134-184) duplicates identical registration logic across visa, safety, facts-country-wrapper, and facts-regions-wrapper files. This pattern appears in all four files with only the function name differing.

Consider extracting this into a shared utility function to reduce duplication and improve maintainability:

/**
 * Registers a block variation when the editor is ready and context matches.
 *
 * @since 2.1.0
 * @param {Function} registrationFn Function that registers the variation.
 * @param {string[]} supportedPostTypes Array of supported post type slugs.
 */
function registerVariationWhenReady(registrationFn, supportedPostTypes) {
    const { select } = wp.data;
    let registered = false;

    const checkAndRegister = () => {
        if (registered) {
            return true;
        }

        const postType = select('core/editor')?.getCurrentPostType();
        const postSlug = select('core/editor')?.getEditedPostSlug();

        if (!postType) {
            return false;
        }

        const isTemplateContext =
            postType === 'wp_template' || postType === 'wp_template_part';

        if (
            supportedPostTypes.includes(postType) ||
            (isTemplateContext &&
                postSlug &&
                (postSlug.includes('destination') ||
                    postSlug.includes('country') ||
                    postSlug.includes('region')))
        ) {
            registrationFn();
            registered = true;
        }

        return registered;
    };

    if (!checkAndRegister()) {
        const interval = setInterval(() => {
            if (checkAndRegister()) {
                clearInterval(interval);
            }
        }, 100);

        setTimeout(() => clearInterval(interval), 5000);
    }
}

Then simplify each block file to:

 wp.domReady(() => {
-    const { select } = wp.data;
-
-    // Define supported post types
-    const supportedPostTypes = ['destination'];
-    let registered = false;
-
-    // Check if current post type is supported
-    const checkAndRegister = () => {
-        if (registered) {
-            return true;
-        }
-
-        const postType = select('core/editor')?.getCurrentPostType();
-        const postSlug = select('core/editor')?.getEditedPostSlug();
-
-        if (!postType) {
-            return false;
-        }
-
-        const isTemplateContext =
-            postType === 'wp_template' || postType === 'wp_template_part';
-
-        if (
-            supportedPostTypes.includes(postType) ||
-            (isTemplateContext &&
-                postSlug &&
-                (postSlug.includes('destination') ||
-                    postSlug.includes('country') ||
-                    postSlug.includes('region')))
-        ) {
-            registerVisaVariation();
-            registered = true;
-        }
-
-        return registered;
-    };
-
-    // Try immediate registration
-    if (!checkAndRegister()) {
-        // If not ready, check periodically
-        const interval = setInterval(() => {
-            if (checkAndRegister()) {
-                clearInterval(interval);
-            }
-        }, 100);
-
-        // Clean up after 5 seconds to prevent infinite checking
-        setTimeout(() => clearInterval(interval), 5000);
-    }
+    registerVariationWhenReady(registerVisaVariation, ['destination']);
 });

src/blocks/safety/index.js (3)

13-132: Add JSDoc documentation for the registration function.

The registerSafetyVariation function lacks JSDoc comments. All functions should include JSDoc with a description, @return tag, and @since tag.

As per coding guidelines.

Apply this diff to add documentation:

+/**
+ * Registers the Safety block variation for destination post types.
+ *
+ * @since 2.1.0
+ * @return {boolean} True if registration succeeded, false otherwise.
+ */
 function registerSafetyVariation() {

---

139-139: Use consistent variable naming across files.

This file uses registeredSafety whilst other block files use registered. Consistent naming improves code readability and maintainability.

Apply this diff for consistency:

-    let registeredSafety = false;
+    let registered = false;

Update all references throughout the domReady callback accordingly.

---

165-168: Remove redundant registration guard.

The inner check if (!registeredSafety) at lines 165-168 is redundant. The checkAndRegister function already returns early at line 143 if registeredSafety is true, making this double-check unnecessary.

Apply this diff to simplify:

-            if (!registeredSafety) {
-                registerSafetyVariation();
-                registeredSafety = true;
-            }
+            registerSafetyVariation();
+            registeredSafety = true;

src/blocks/facts-country-wrapper/index.js (1)

13-123: Add JSDoc documentation for the registration function.

The registerFactsCountryWrapperVariation function lacks JSDoc comments. All functions should include JSDoc with a description, @return tag, and @since tag.

As per coding guidelines.

Apply this diff to add documentation:

+/**
+ * Registers the Country block variation for destination post types.
+ *
+ * @since 2.1.0
+ * @return {boolean} True if registration succeeded, false otherwise.
+ */
 function registerFactsCountryWrapperVariation() {

src/blocks/facts-regions-wrapper/index.js (1)

13-123: Add JSDoc documentation for the registration function.

The registerFactsRegionsWrapperVariation function lacks JSDoc comments. All functions should include JSDoc with a description, @return tag, and @since tag.

As per coding guidelines.

Apply this diff to add documentation:

+/**
+ * Registers the Regions List block variation for destination post types.
+ *
+ * @since 2.1.0
+ * @return {boolean} True if registration succeeded, false otherwise.
+ */
 function registerFactsRegionsWrapperVariation() {

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro