What problem does this feature proposal attempt to solve?
Community feedback has shown that the default resolver from webonyx/graphql-php may not be optimally suited for a Laravel application and there is potential for improvement.
Because the default resolver is called very often, we have to consider performance.
Which possible solutions should be considered?
Given Eloquent models are probably the most common returned data type, we could optimize for them.
Changing the default resolver is documented here, but could perhaps be simplified through the config.
What problem does this feature proposal attempt to solve?
Community feedback has shown that the default resolver from
webonyx/graphql-phpmay not be optimally suited for a Laravel application and there is potential for improvement.Because the default resolver is called very often, we have to consider performance.
Which possible solutions should be considered?
Given Eloquent models are probably the most common returned data type, we could optimize for them.
Changing the default resolver is documented here, but could perhaps be simplified through the config.