Kai Ren

@LegNeato what about finishing this feature? I've recently received a lot of feedback from different people looking for such feature. It seems that passing schemaless opaque JSON is quite widely...

@nlinker OK, that's easy with output, but I'm unsure about input. Whether the complex JSON object will be parsed OK as field input argument. Would you be so kind to...

@Mcat12 so this PR makes `juniper` usable only with single-threaded runtimes, right? If so, I'm very unsure this chage worth such an impact. Maybe it's better to use [`send_wrapper`](https://docs.rs/send_wrapper) where...

@Mcat12 the biggest blocker is GAT, of course. The fact that `juniper` cannot be `Send`/`Sync` transparent is due to trait objects usage in traits. I've played with this multiple times...

@DusterTheFirst we need a concrete Rust type to be named for building up a GraphQL schema by introspecting the Rust code given to macros. Unfortunately, having `UserId` type and `ToString::to_string`...

@cyberhck yes, federation is definitely in our plans. Contributions are welcome, though, as the project has quite a low bandwidth at the moment.

@vuldin from what is written in the blogpost you've linked, there shouldn't be any troubles with the license, until the juniper maintainers will decide to sell it as a "managed...

@frederikhors from [what I see](https://entgo.io/docs/tutorial-todo-gql-field-collection/#ent-solution): > The Ent extension for field collection adds support for automatic [GraphQL fields collection](https://spec.graphql.org/June2018/#sec-Field-Collection) for associations (i.e. edges) using [eager loading](https://entgo.io/docs/eager-load). May be this crate...

@MikailBag for N + 1 query problem the usual solution is either [dataloader](https://github.com/cksac/dataloader-rs) or [lookahead](https://github.com/graphql-rust/juniper/issues/387). As for proposed solution I'm unsure how well it will fit. Usually, resolvers may contain...

@ilslv I don't really like the idea of pushing users to something. We have already possibility to provide `From` for another struct. Having ` #[graphql(ignore)]` _in addition to that_ will...