You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if batched queries are currently executed synchronously or asynchronously, but I could imagine there would be great performance benefits if they were resolved asynchronously. @spawnia could you confirm? It looks like you have been working on the ReactPromiseAdapter recently and I'm not sure if that is related. 👀
I am all over the graphql-php codebase, mostly working on strict typing and uncovering/fixing bugs. Have not paid particular attention to async execution.
Your assumption seems sound, I think it is very much possible and useful for Lighthouse to allow alternative executors. Open for pull requests 😉
What problem does this feature proposal attempt to solve?
It looks like webonyx/graphql-php can fetch data asynchronously. https://webonyx.github.io/graphql-php/data-fetching/#async-php
I'm not sure if batched queries are currently executed synchronously or asynchronously, but I could imagine there would be great performance benefits if they were resolved asynchronously. @spawnia could you confirm? It looks like you have been working on the
ReactPromiseAdapter
recently and I'm not sure if that is related. 👀https://github.com/webonyx/graphql-php/commits/master/src/Executor/Promise/Adapter/ReactPromiseAdapter.php
Which possible solutions should be considered?
I assume we could allow an alternate path for execution here if we wanted to use
promiseToExecute()
:lighthouse/src/GraphQL.php
Lines 159 to 165 in 985d39e
And I'm also naively assuming that it should just work but let me know what you think.
The text was updated successfully, but these errors were encountered: