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
As per this comment, I'm wondering if GraphQL::setPromiseAdapter(), and Executor::setPromiseAdapter() and Executor::getPromiseAdapter() shouldn't be deprecated.
Seems logical as GraphQL::execute() and GraphQL::executeAndReturnResult() have been deprecated a long time ago, GraphQL::promiseToExecute() doesn't need them and GraphQL::executeQuery() doesn't use them.
Having them deprecated would IMO make more obvious how to set up custom promise adapters correctly.
As per this comment, I'm wondering if
GraphQL::setPromiseAdapter()
, andExecutor::setPromiseAdapter()
andExecutor::getPromiseAdapter()
shouldn't be deprecated.Seems logical as
GraphQL::execute()
andGraphQL::executeAndReturnResult()
have been deprecated a long time ago,GraphQL::promiseToExecute()
doesn't need them andGraphQL::executeQuery()
doesn't use them.Having them deprecated would IMO make more obvious how to set up custom promise adapters correctly.
Context: overblog/dataloader-php#39. Also related to #664.
The text was updated successfully, but these errors were encountered: