title: "feat: lazy loading fields for Object Types and Interface Types"

pr: 3356

author: "jasonbahl"

type: "feat"

breaking: false

This PR introduces lazy evaluation of GraphQL field definitions through callable functions in the core type system. The key changes focus on:

1. Added support in \`WPInterfaceTrait\` to handle callable field definitions:

\`\`\`php

if ( is_callable( $config['fields'] ) ) {

$config['fields'] = $config['fields']();

}

2. Modified \`WPInterfaceType\` and \`WPObjectType\` to use callable functions for field definitions:

\`\`\`php

$config['fields'] = function () use ( $config ) {

return ! empty( $this->fields ) ? $this->fields : $this->get_fields( $config, $this->type_registry );

};

This architectural change defers the execution of field definitions until they are actually needed, rather than defining all fields upfront during schema initialization.

Here's an example of how the \`User\` type fields were refactored:

**Before:**

\`\`\`php

'fields' => [

'id' => [

'description' => __( 'The globally unique identifier for the user object.', 'wp-graphql' ),

],

'name' => [

'type' => 'String',

'description' => __( 'Display name of the user.', 'wp-graphql' ),

],

// ... more fields

**After:**

\`\`\`php

'fields' => static function () {

return [

'id' => [

'description' => __( 'The globally unique identifier for the user object.', 'wp-graphql' ),

],

'name' => [

'type' => 'String',

'description' => __( 'Display name of the user.', 'wp-graphql' ),

],

// ... more fields

];

}

To measure the impact of this change, we added a \`TestGetText\` class that tracks all \`__()\` function calls during schema generation and query execution. This logging shows that translations are now only executed when fields are actually queried, rather than during schema initialization.

\`\`\`php

class TestGetText {

/**

* @var array

*/

protected $gettext_log = [];

/**

* Constructor

*/

public function __construct() {

// Reset at the very start of schema generation

add_action( 'graphql_process_http_request', [ $this, 'init_log' ], 1 );

// Track all translations

add_filter(

'gettext',

function ( $text ) {

$this->gettext_log[] = $text;

return $text;

},

10,

3

);

// Add to extensions

add_filter( 'graphql_request_results', [ $this, 'add_to_extensions' ], 10, 1 );

}

/**

* Initialize the log

*/

public function init_log(): void {

$this->gettext_log = [];

}

/**

* Add translation data to GraphQL extensions

*

* @param \GraphQL\Executor\ExecutionResult $response The GraphQL response

*/

public function add_to_extensions( \GraphQL\Executor\ExecutionResult $response ): \GraphQL\Executor\ExecutionResult {

$extensions = $response->extensions ?? [];

$extensions['translations'] = [

'count' => count( $this->gettext_log ),

// 'log' => $this->gettext_log,

];

$response->extensions = $extensions;

return $response;

}

}

new TestGetText();

Working on #3354 (more to come)

This change provides significant performance benefits by:

1. **Deferred Translation**: The \`__()\` function calls for field descriptions are now only executed when the fields are actually used in a query, rather than during schema initialization. This is particularly important for multilingual sites where translation lookups can be expensive.

2. **Reduced Memory Usage**: Field definitions that are rarely used in queries no longer need to be stored in memory during the entire request lifecycle.

3. **Faster Schema Initialization**: The schema can be initialized more quickly since field definitions are not processed until they are actually needed.

4. **Better Resource Management**: Resources like database connections or complex calculations needed for field definitions are only allocated when the fields are actually queried.

The changes maintain full backward compatibility while providing these performance improvements. All existing functionality remains the same, but the implementation is now more efficient, especially for large WordPress installations with complex schemas.

title: "chore: add array shapes to and "

pr: 3366

author: "justlevine"

type: "chore"

breaking: false

This PR fixes the use of \`mixed\` in iterable types inside the \`Admin\Extensions\` and \`Admin\AdminNotices\` class. The only remaining uses of mixed in that class are intentional: i.e. when we're trying to validate if a filtered list of extensions has the necessary data.

Additionally, native types have been implemented in all places in those classes where to do so would not cause any breakings.

There are _no_ breaking or user-facing changes in this PR.

title: "chore: improve type-safety for class"

pr: 3367

author: "justlevine"

type: "chore"

breaking: false

This PR:

- Inlines all (backwards-compatible) PHPDoc types into their native PHP types

- Replaces the use of \`mixed\` with the specific array shape (_where possible_)

- Adds type-narrowing to \`WPGraphQL::get_allowed_post_types()\` and \`::get_allowed_taxonomies()\`, so the correct traversable type of the array is hinted correctly.

References to these functions have been cleaned up accordingly (usually just by removing a \`/** @var {...} */\` typehint.

There are _no_ breaking changes in this PR.

title: "fix: don't initialize twice in class constructor"

pr: 3369

author: "justlevine"

type: "fix"

breaking: false

This PR fixes a bug in the \`Request::__construct()\` method, where the \`->app_context\` was previously initialized twice.

Now it's only initialized once, while the \`$type_registry\` continues to be injected onto the AppContext class at the same point of the lifecycle.

// Bail if debug is disabled.

if ( ! WPGraphQL::debug() ) {

return;

}

// Reset the introspection query flag

WPGraphQL::set_is_introspection_query( false );