Actions

Fires after themes have been setup, allowing for both plugins and themes to register things before graphql_init

Fire an action when the Type Register is returned

Fire an action when the Schema is returned

Fire an action as the type registry is initialized. This executes before the graphql_register_types action to allow for earlier hooking

Fires when the debug logs are retrieved

Run an action when the WPObjectType is instantiating

Run an action when the WPObjectType is instantiating

Run an action after the additional data has been updated. This is a great spot to hook into to update additional data related to users, such as setting relationships, updating additional usermeta, or sending emails to Kevin… whatever you need to do with the userObject

Fire an action as the type registry is initialized. This executes during the graphql_register_types action to allow for earlier hooking

Fires an action as the Type registry is being initiated

Fires an action when a term is updated via a GraphQL Mutation

Allow additions to the bottom of the GraphQL settings form

Allow additions to the top of the GraphQL settings form

Action that fires when settings are being initialized

Action to hook into to register settings

Run an action after the HTTP Response is ready to be sent back. This might be a good place for tools to hook in to track metrics, such as how long the process took from graphql_process_http_request to here, etc.

This action can be hooked to to enable various debug tools, such as enableValidation from the GraphQL Config

Fires an action when the headers are set

Run an action when the server config is created. The config can be acted upon directly to override default values or implement new features, e.g., $config->setValidationRules()

Run an action for reach request

Run an action after the response has been filtered, as the response is being returned. This is a good place for debug tools to hook in to log things, etc.

Run an action. This is a good place for debug tools to hook in to log things, etc.

Action that executes when a GraphQL Request begins. This is a great place for plugins to hook in and modify things that should only occur in the context of a GraphQL Request. The base class hooks into this action to kick off the schema creation, types are not set up until this action has run.

Fires after a single term is created or updated via a GraphQL mutation

Fire an action before setting object terms during a GraphQL Post Object Mutation. One example use for this hook would be to create terms from the input that may not exist yet, so that they can be set as a relation below.

Run an action after the additional data has been updated. This is a great spot to hook into to update additional data related to postObjects, such as setting relationships, updating additional postmeta, or sending emails to Kevin. . . whatever you need to do with the postObject.

Hook that fires after the data is returned for the field

Run an action after the additional data has been updated. This is a great spot to hook into to update additional data related to mediaItems, such as updating additional postmeta, or sending emails to Kevin. . .whatever you need to do with the mediaItem.

Fire an action AFTER the field resolves

Fire an action BEFORE the field resolves

Fires an action when comment meta is updated

Fire an action as the type registry is initialized. This executes before the graphql_register_types action to allow for earlier hooking