Problem/Motivation

With the deprecation of callbacks, we should get to a resolver registry that can be fully serialized. When we do this we can skip the discovery and instantiation of all the extension plugins since they would no longer be needed.

We want to provide space for this caching in a future minor version and should take care to break the SdlSchemaPluginBase API now so that this can be implemented without breaking changes later.

Steps to reproduce

Proposed resolution

Ensure that the methods for retrieving the registry and building the registry are split out. This allows the retrieval of the registry to be cached while downstream modules implement the building of the registry only.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork graphql-3586928

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

kingdutch created an issue. See original summary.

klausi’s picture

Status: Active » Reviewed & tested by the community

Thanks, looks goof to me!

kingdutch’s picture

Assigned: kingdutch » Unassigned
Status: Reviewed & tested by the community » Fixed
Issue tags: +DevDaysAthens2026

Thanks for the review! Added a change record and merged the PR :)

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

  • kingdutch committed 2a26a917 on 5.x
    feat: #3586928 Split resolver registry init, build, and retrieve...
kingdutch’s picture

Issue summary: View changes

I forgot to fill the issue with some actual reasoning and goals.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.