David Pedersen

Nope you don’t need to do anything. I’ll take a look this week :)

juniper-eager-loading doesn't require that your structs map directly to your database schema. So you're fully able to make structs that compose several database models. Doing that will require implementing [`EagerLoadChildrenOfType`](https://docs.rs/juniper-eager-loading/0.5.0/juniper_eager_loading/trait.EagerLoadChildrenOfType.html)...

Are you able to share all your code so I can poke around? A repo I could fork/clone would be ideal.

If you need hyper 1.0 support you should be able to use https://crates.io/crates/tower-hyper-http-body-compat

I'm not sure. Haven't actually done it myself. I tried getting a small example working but kept running into connection issues: ```rust use std::{ future::Future, pin::Pin, task::{Context, Poll}, }; use...

Good catch. I would like to get https://github.com/davidpdrsn/juniper-from-schema/pull/74 merged first so we don't have to migrate more `graphql_object!` macro code to `juniper::object`. That PR is currently blocked by https://github.com/graphql-rust/juniper/pull/441. I...

Note to self: I would also be cool to explore the context being generic over one or more lifetimes.

We need to get some more clarity on whether this is a bug or just how h2 works. I don't know enough about the lower levels to know. We'd also...

> btw.: currently routing::tests::logging_rejections fails for me (also fails on main) unless I pass some -F tracing,headers to cargo test That's intentional. We require all features for tests. The additional...

Unfortunately I haven't had the time and motivation lately to work on this. I don't work with graphql professionally anymore and most of my time is spent on axum and...