Actions

Actions let your code run at specific points in the WPGraphQL request lifecycle without changing the value being processed. Below are the actions WPGraphQL provides for you to hook into.

Debugging and Instrumentation

• graphql_after_resolve_field

  Fire an action AFTER the field resolves

• graphql_before_resolve_field

  Fire an action BEFORE the field resolves

• graphql_determine_graphql_keys

  Fires after QueryAnalyzer has calculated list/query/model keys for a request.

• graphql_get_debug_log

  Init the debug logger

Model Layer

• graphql_after_return_field_from_model

  Hook that fires after the data is returned for the field

• graphql_comment_object_mutation_update_additional_data

  Fires after additional comment mutation data has been updated.

• graphql_insert_post_object

  Fires after a single term is created or updated via a GraphQL mutation The dynamic portion of the hook name, $taxonomy->name refers to the taxonomy of the term being mutated

• graphql_insert_term

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

• graphql_media_item_mutation_update_additional_data

  Run an action after the additional data has been updated.

• graphql_post_object_mutation_set_object_terms

  Fire an action before setting object terms during a GraphQL Post Object Mutation.

• graphql_post_object_mutation_update_additional_data

  Run an action after the additional data has been updated.

• graphql_update_term

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

• graphql_user_object_mutation_update_additional_data

  Run an action after the additional data has been updated.

Request Lifecycle

• do_graphql_request

  Run an action for each request.

• graphql_after_execute

  Run an action after GraphQL Execution

• graphql_before_execute

  This action runs before execution of a GraphQL request (regardless if it’s a single or batch request)

• graphql_execute

  Run an action.

• graphql_execute_batch_queries

  Execute batch queries

• graphql_init

  Fire off init action

• graphql_mutation_response

  Fires after the mutation payload has been returned from the mutateAndGetPayload callback.

• graphql_process_http_request

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

• graphql_process_http_request_response

  Run an action after the HTTP Response is ready to be sent back.

• graphql_response_set_headers

  Fire an action when the headers are set

• graphql_return_response

  Run an action after the response has been filtered, as the response is being returned.

• graphql_server_config

  Run an action when the server config is created.

• init_graphql_request

  Fires when initializing a GraphQL request from WP-CLI.

• init_graphql_request

  Action – intentionally with no context – to indicate a GraphQL Request has started.

Schema Registration

• graphql_get_schema

  Fire an action when the Schema is returned

• graphql_get_type_registry

  Fire an action when the Type Registry is returned

• graphql_register_initial_types

  Fire an action as the type registry is initialized.

• graphql_register_types

  Fire an action as the type registry is initialized.

• graphql_register_types_late

  Fire an action as the type registry is initialized.

• graphql_wp_connection_type

  Run an action when the WPConnectionType is instantiating.

• graphql_wp_mutation_type

  Run an action when the WPMutationType is instantiating.

• graphql_wp_object_type

  Run an action when the WPObjectType is instantiating

• graphql_wp_union_type

  Fires after a WPUnionType has been configured and before registration.

• init_graphql_type_registry

  Fire an action as the Type registry is being initiated.

Settings and Admin

• enqueue_graphiql_extension

  Fires before GraphiQL extensions are enqueued.

• graphql_admin_notices_init

  Fires when admin notices are initialized.

• graphql_admin_notices_render_notice

  Fires for each admin notice that is rendered.

• graphql_admin_notices_render_notices

  Fires before the admin notices are rendered.

• graphql_do_update_routine

  Fires the update routine.

• graphql_experiments_loaded

  Fires after all the experiments have been loaded.

• graphql_experiments_registered

  Fires after the experiment classes have been registered.

• graphql_init_settings

  Fires before WPGraphQL settings sections and fields are registered.

• graphql_register_settings

  Fires after core WPGraphQL settings have been registered.

• graphql_settings_enqueue_scripts

  Fires when WPGraphQL settings assets should be enqueued.

• graphql_settings_form_bottom

  Fires after rendering a WPGraphQL settings form section.

• graphql_settings_form_top

  Fires before rendering a WPGraphQL settings form section.