Miaxos

Well, in fact when you use the `#[Object]` macro, there is a bunch of stuff going on, and one of those is to create an impl for the `ContainerType` actually...

For referencee, I proposed 'ResolverError' first thinking of a previous implementation we did at work: Errors are implemented by implementing a trait which will tell: - Should we stop the...

>I can't design a more convenient API without generic specialization, so I can only keep ResolverError. 😒 Haha, I'm also looking forward to the specialization feature 😁! I will try...

Yes you can with this: `async_graphql::context::QueryEnv::create_context` these methods & structs are hidden from documentation but you can use it inside your tests.

I'm using it at [Brevz](https://brevz.io)! it's really an awesome crates to use, incredible project!

> I would expect async-graphql to append the additional fields type names to the generated connection type when different from EmptyFields, or provide a way to define the output type...

>I find that a little surprising. I would have expected a follow up request that ended in error to try again (and produce a new error if it fails again)....

Hello! >I'm writing to you because I just found out an excellent feaure of Ent: [GraphQL Field Collection](https://entgo.io/docs/tutorial-todo-gql-field-collection). The example is flawed, with dataloader you can do the same as...

Yep you are right, I didn't understand you only wanted the endpoint to store the queries. But for `async-graphql` to work when a relay client ask for a persisted query,...

Absolutely! We could do it with the `derived` attribute behind the `chrono` feature gate instead of multiple feature gates