5 ms·
I've been using this for a small project and the feature set is far more comprehensive than anything else I've seen in Rust. In comparison to Juniper, it has mu
by unignorant 6y ago
I've been using this for a small project and the feature set is far more comprehensive than anything else I've seen in Rust. In comparison to Juniper, it has much better support for subscriptions in particular. Its creator has been amazingly productive and continues to add features almost daily.
- jkoudys 6y agoCame here to ask how it compares to juniper. Juniper has been the one part of my stack of crates that's made async difficult for a while now. Building a rust app with full futures support from top to bottom has huge benefits, but support on juniper has been slow in coming (a lot of existing code to move along with it), and the main error being GraphQLError<'a> with a lifetime and no impl of std::error::Error has been a huge nuisance to deal with. That said, constructing the resolvers with the `#[juniper::graphql_object` macro has been incredibly easy. They used to use some clunky DSL, but since the move it's been great. Don't think I'd consider moving if async-graphql isn't as strong on that, but I won't really know until I try both.
- LegNeato 6y agoJuniper master has async and subscription support
- jkoudys 6y agoYeah I've been using it - took a while but pretty happy with it so far.
- unignorant 6y agoConstructing the resolvers is very similar to Jupiter, see: https://github.com/async-graphql/examples/blob/master/models/books/src/lib.rs#L36 https://github.com/async-graphql/examples/blob/master/models... Agree that it's really nice. I wouldn't have switched either without that feature.
- sunli829 6y agoThanks for your support. :)