Fix: Back-port compatibility fixes for wp-graphql-content-blocks to SnapWP Helper plugin

[Ta5r]

What

In this PR, I backported specific compatibility fixes from wp-graphql-content-blocks to snapwp-helper to resolve issues noted in issue #224. The main updates include adjustments to the ContentBlocksResolver.php and the SchemaFilters.php file.

Why

This change is necessary because snapwp-helper was getting incompatible with WPGraphQL Content Blocks 4.2.0. This incompatibility was causing issues. Backporting these changes allows snapwp-helper to remain compatible with WPGraphQL Content Blocks plugin.

Related Issue(s):

Closes https://github.com/rtCamp/headless/issues/231

How

1. Reviewed Fixes: I focused on the relevant code sections in snapwp-helper#25 and wp-graphql-content-blocks#31, specifically examining:

• src/Modules/GraphQL/Data/ContentBlocksResolver.php
• src/Modules/GraphQL/SchemaFilter.php

2. Backported Compatibility Changes: I back ported over the necessary code from wp-graphql-content-blocks into snapwp-helper.

Testing Instructions

1. Open GraphiQL IDE.
2. Enter the following query:

query GetCurrentTemplate($uri: String!) {
  templateByUri(uri: $uri) {
    editorBlocks {
      name
      ... on CoreQueryNoResults{
        renderedHtml
      }
    }
  }
}

3. Expect the following response (pfa screenshot)

Screenshots

Checklist

• I have read the Contribution Guidelines.
• My code is tested to the best of my abilities.
• My code passes all lints (PHPCS, PHPStan, ESLint, etc).
• My code has detailed inline documentation.
• I have added unit tests to verify the code works as intended.
• I have updated the project documentation accordingly.

[Ta5r]

Desired results of query in GraphiQL IDE :

(debug mode on)

Results from my work :

(debug mode on)

[justlevine]

Overall the backport looks good.

Fix the comments, fill out the PR description and this should be ready.

[justlevine]

This is why we're not getting the inner blocks - you got rid of the graphql_object_fields filter which let us overload the entire class, and instead are only overloading the internal handle_do_block().

Revert this and your PR should be working.

[Ta5r]

Donew ✅

[justlevine]

Remove this it's unused and removed in v4.2.0

[Ta5r]

Removed 🚀

[Ta5r]

Desired response :

Response achieved ✅ :

The error section for both the responses for the following given query are same with the following debugMesasge and the data section are also showing same and complete desired results ✅ .

Query:

query GetCurrentTemplate($uri: String!) {
  templateByUri(uri: $uri) {
    editorBlocks {
      name
      ... on CoreQueryNoResults{
        renderedHtml
      }
    }
  }
}

Response:

"debugMessage": "Attempt to assign property \"parsed_block\" on null",

🚀 🚀 🚀