Error handling

Resolve can return a Result, which has the following definition:

type Result<T> = std::result::Result<T, Error>;

Any Error that implements std::fmt::Display can be converted to Error and you can extend the error message.

The following example shows how to parse an input string to an integer. When parsing fails, it will return an error and attach an error message. See the Error Extensions section of this book for more details.

fn main() {
extern crate async_graphql;
use std::num::ParseIntError;
use async_graphql::*;

struct Query;

impl Query {
    async fn parse_with_extensions(&self, input: String) -> Result<i32> {
            .map_err(|err: ParseIntError| err.extend_with(|_, e| e.set("code", 400)))?)

Errors in subscriptions

Errors can be returned from subscription resolvers as well, using a return type of the form:

async fn my_subscription_resolver(&self) -> impl Stream<Item = Result<MyItem, MyError>> { ... }

Note however that the MyError struct must have Clone implemented, due to the restrictions placed by the Subscription macro. One way to accomplish this is by creating a custom error type, with #[derive(Clone)], as seen here.