Simon Westlake
Simon Westlake
Yes, it is tricky. There are some ways around the global tracer issue - Swoole for example has a sandbox that is used to separate per-request items out. That being...
Yep, exactly. Just treat each request as independent. I think this might be fairly easy to do by hooking into the `onRequest` method.. I'm planning to take a look at...
This is great, I have built something internally to use (as I don't use Eloquent for this API) and it is a crucial part of building a scalable GraphQL API....
You can specify an error handler, see 'error_formatter' in the graphql.php config file. This intercepts Exceptions before they're passed back to the consumer - I just call $e->getPrevious() here, and...
I am very interested in this as well, is it on the roadmap?
I would expect to have to implement the actual resolution of subscriptions on my side (although some helper to pass in data and return the query parameters only would be...
Yes, that's exactly what I'm thinking. In fact, I would hazard a guess that a subscription can really just implement an existing query class, but the 'subscription' prefix would trigger...
I'm going to have to start working on this for myself soon. I will fork and submit a PR when done, but I'm not sure it will be abstract enough...
No, I ended up finding that subscriptions weren't really a good solution for my needs. I went in a different direction.
Implementing subscriptions would definitely be a great feature!