Filters

Filters the field used for ordering connection queries when cursors are used for pagination

Given a string, and optional context, this decodes html entities if html_entity_decode is enabled

Filter the config of WPUnionType

Filter the possible_types to allow systems to add to the possible resolveTypes.

Filter the resolve type method for all unions

Set the $filterable_config as the $config that was passed to the WPSchema when instantiated

Filter WPScalar config

Filter all object fields, passing the $typename as a param. This is useful when several different types need to be easily filtered at once. . .for example, if ALL types with a field of a certain name needed to be adjusted, or something to that tune.

Filters the interfaces applied to an object type

Filter the config of WPObjectType

Filter all object fields, passing the $typename as a param.

Filter the config of WPInterfaceType

Filter the resolve type method for all interfaces

Filter all object fields, passing the $typename as a param.

Allow the request data to be filtered. Previously this filter was only applied to non-HTTP requests. Since 0.2.0, we will apply it to all requests.

Pass the enum values through a filter

Filters the mappings for input to arguments

Filters all of the fields available for input

Filter the input fields. This allows plugins/themes to hook in and alter what $args should be allowed to be passed from a GraphQL Query to the WP_User_Query.

Filter the trace

Filter whether the logs can be seen in the request results or not

Filter the $insert_args

Filter the input fields. This allows plugins/themes to hook in and alter what $args should be allowed to be passed from a GraphQL Query to the get_terms query.

Filter the query_args that should be applied to the query. This filter is applied AFTER the input args from the GraphQL Query have been applied and has the potential to override the GraphQL Query Input Args.

Filter the settings sections

Filter the setting field config

Filter the $status_code before setting the headers

Filter the $headers to send

Filter to determine if nocache headers are sent on authenticated requests.

Filtered list of access control headers

Filter the headers

Filter whether the request is a GraphQL HTTP Request. Default is false, as the majority of WordPress requests are NOT GraphQL requests (at least today that’s true ????).

Filter whether the request is a GraphQL HTTP Request. Default is null, as the majority of WordPress requests are NOT GraphQL requests (at least today that’s true ????).

Pass the route through a filter in case the endpoint /graphql should need to be changed

Filter the $response of the GraphQL execution. This allows for the response to be filtered before it’s returned, allowing granular control over the response at the latest point.

If false, there are no authentication errors. If true, execution of the GraphQL request will be prevented and an error will be thrown.

Return the filtered root value

Return the validation rules to use in the request

Filter whether the logs can be seen in the request results or not

Filter whether to allow terms to be created during a post mutation.

Sets the post lock

Filter the $insert_post_args

Determine whether the intended status should be set or not. By filtering to false, the $intended_post_status will not be set at the completion of the mutation.

Filter the default post status to use when the post is initially created. Pass through a filter to allow other plugins to override the default (for example, Edit Flow, which provides control over customizing statuses or various E-commerce plugins that make heavy use of custom statuses)

Filter the input fields. This allows plugins/themes to hook in and alter what $args should be allowed to be passed from a GraphQL Query to the WP_Query.

Filter the $query args to allow folks to customize queries programmatically

Filters whether to resolve revision metadata from the parent node by default.

Filter the array of fields for the Model before the object is hydrated with it

Filter the data returned by the default callback for the field

Filter to short circuit the callback for any field on a type. Returning anything other than null will stop the callback for the field from executing, and will return your data or execute your callback instead.

Capability to check required for the field

Filter for the allowed restricted fields

Filter the visibility name to be returned

Filter to determine if the data should be considered private or not

Filter for the capability to check against for restricted data

Allow users to override how nav menu items are resolved. This is useful since we often add taxonomy terms to menus but would prefer to represent the menu item in other ways, e.g., a linked post object (or vice-versa).

Filter the $insert_post_args

Filter the auth error

Fire an action before the field resolves

When this filter return anything other than the $nil it will be used as the resolved value and the execution of the actual resolved is skipped. This filter can be used to implement field level caches or for efficiently hiding data by returning null.

Filter the field definition

Return the filtered debug log

Filter the log entry for the debug log

Add a filter to allow externally registered node types to return the proper type based on the node_object that’s returned

Filter the $allowed_settings to allow some to be enabled or disabled from showing in the GraphQL Schema

Filter the $allowed_settings_by_group to allow enabling or disabling groups in the GraphQL Schema

Filters the ORDER BY clause of the query

Filters the WHERE clause of the query.

Filter the $insert_post_args

Filter the input fields. This allows plugins/themes to hook in and alter what $args should be allowed to be passed from a GraphQL Query to the get comments query.

Filter the query_args that should be applied to the query. This filter is applied AFTER the input args from the GraphQL Query have been applied and has the potential to override the GraphQL Query Input Args.

This filters the config for the AppContext. This can be used to store additional context config, which is available to resolvers throughout the resolution of a GraphQL request.

This filters the data loaders, allowing for additional loaders to be added to the AppContext or for existing loaders to be replaced if needed.

Filter to determine if GraphiQL should be enabled.

Filter the model before returning.

This filter allows the model generated by the DataLoader to be filtered. Returning anything other than null here will bypass the default model generation for an object.

Filter the connection. In some cases, connections will want to provide additional information other than edges, nodes, and pageInfo. This filter allows additional fields to be returned to the connection resolver

Filters the edges in the connection

Set the items. These are the “nodes” that make up the connection. Filters the nodes in the connection.

Filter the connection IDs

Set the query for the resolver, for use as reference in filters, etc

Check if the connection should execute. If conditions are met that should prevent the execution, we can bail from resolving early, before the query is executed.

Filter the pageInfo that is returned to the connection.

Create the edge, pass it through a filter.

This filter allows to modify the requested connection page size

Filter the maximum number of posts per page that should be queried. The default is 100 to prevent queries from being exceedingly resource intensive, however individual systems can override this for their specific needs. This filter is intentionally applied AFTER the query_args filter.

Get the Query Args. This accepts the input args and maps it to how it should be used in the WP_Query.

Generate & Filter the schema.

Filter to determine if GraphQL Debug is enabled

Filter the Schema

Returns the array of $allowed_taxonomies

Define the $allowed_post_types to be exposed by GraphQL Queries Pass through a filter to allow the post_types to be modified (for example if a certain post_type should not be exposed to the GraphQL API)

This filter can be used to disable or enable the GraphQL Admin pages with code.