faustjs icon indicating copy to clipboard operation
faustjs copied to clipboard

Evaluate plugin after new release of WPGraphQL 2.3.0

Open colinmurphy opened this issue 8 months ago • 1 comments

As part of the WPGraphQL 2.3.0 release - https://github.com/wp-graphql/wp-graphql/releases/tag/v2.3.0

There was signifcant improvements made around callbacks - https://github.com/wp-graphql/wp-graphql/pull/3356

We should evaluate the codebase of this plugin and see if we can make some improvements to how we make callbacks

colinmurphy avatar May 09 '25 14:05 colinmurphy

I see you plan on improvements of the packages, here is just a heads up that there are currently these issues I have observed (maybe more), after updating wp-graphql to version 2.3.0 and running FE app with currently the latest Faust packages:

    "@faustwp/block-editor-utils": "0.3.3",
    "@faustwp/blocks": "6.1.2",
    "@faustwp/cli": "3.2.3",
    "@faustwp/core": "3.2.3",

and

"wpackagist-plugin/faustwp": "1.8.0",

Observed issues:

debug - Faust is running in debug mode
(node:65343) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:65343) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
debug - Discoverd GraphQL endpoint at https://gadoe.test/index.php?graphql
debug - "faust generatePossibleTypes" failed with the following error:  Error: There were errors in the GraphQL request: Internal server error
    at generatePossibleTypes (file:///Users/plev/Sites/gadoe.test/frontend-faustjs/node_modules/@faustwp/cli/dist/generatePossibleTypes.js:37:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async file:///Users/plev/Sites/gadoe.test/frontend-faustjs/node_modules/@faustwp/cli/dist/index.js:46:13
error - Unable to update this project's possibleTypes schema
error - Make sure the FAUST_SECRET_KEY value in your environment matches the value in the Faust WordPress plugin settings, or that you have "Enable Public Introspection" checked in WPGraphQL if not using FAUST_SECRET_KEY: https://gadoe.test/wp-admin/admin.php?page=graphql-settings

and with graphql-codegen command:

 Parse Configuration
❯ Generate outputs
✔ Parse Configuration
⚠ Generate outputs
  ❯ Generate to ./__generated__/
    ✖ Failed to load schema from https://gadoe.test/wp/graphql:
      Internal server error

      GraphQL Code Generator supports:

      - ES Modules and CommonJS exports (export as default or named export "schema")
      - Introspection JSON File
      - URL of GraphQL endpoint
      - Multiple files with type definitions (glob expression)
      - String in config file

      Try to use one of above options and run codegen again.

    ◼ Load GraphQL documents
    ◼ Generate

Current workaround is to downgrade wp-graphql to previous version 2.1.1. Thank you in advance for looking in these.

jan-clockworkwp avatar May 19 '25 10:05 jan-clockworkwp