Is there a way to trigger a query with all of it's resolvers without using ::query()?

[drewgallagher]

hey quick question, is there a way to trigger a query or mutation (and all of its nested resolvers) without calling GraphQL::query() directly?

I have a query that returns a bunch of fields, some of which are calculated in nested resolvers. I need to export that data into a CSV, but running the query itself takes too long and times out, so I’m trying to handle it in a background job instead.

Right now I’m using a workaround that AI suggested, which is to call the query from inside the job using GraphQL::query() so that everything gets resolved first, and then process that data for the export. it works, but it feels a bit hacky.

is there a better way to run the resolver tree and get the fully resolved data from a job, without going through the full HTTP flow or using the GraphQL::query() helper?

[mfn]

Sounds like a duplicate of #1191

Please don't create multiple discussion regarding the same issue