Field argument descriptions don't get applied if using raw identifier in `arguments`

[davidpdrsn]

This is quite an obscure bug that I doubt many will run into, but I did hit while building juniper-from-schema.

Describe the bug
If you define an object like this:

#[graphql_object]
impl Query {
    #[graphql(
        arguments(
            a(description = "foo"),
            b(description = "bar"),
        )
    )]
    fn add(a: i32, b: i32) -> i32 {
        a + b
    }
}

Then the docs on the arguments show up just fine in GraphiQL.

However if you use raw identifiers

#[graphql_object]
impl Query {
    #[graphql(
        arguments(
            r#a(description = "foo"),
            r#b(description = "bar"),
        )
    )]
    fn add(r#a: i32, r#b: i32) -> i32 {
        a + b
    }
}

Then they don't show up

To Reproduce
Example warp app with GraphiQL that I used for debugging this

use juniper::*;
use warp::Filter;

type Schema = RootNode<'static, Query, EmptyMutation<()>, EmptySubscription<()>>;

fn schema() -> Schema {
    Schema::new(
        Query,
        EmptyMutation::<()>::new(),
        EmptySubscription::<()>::new(),
    )
}

struct Query;

#[graphql_object]
impl Query {
    #[graphql(
        arguments(
            r#a(description = "foo"),
            r#b(description = "bar"),
        )
    )]
    fn add(r#a: i32, r#b: i32) -> i32 {
        a + b
    }
}

#[tokio::main]
async fn main() {
    let state = warp::any().map(move || ());

    let graphql_filter = juniper_warp::make_graphql_filter(schema(), state.boxed());

    let graphiql_filter = warp::get()
        .and(warp::path("graphiql"))
        .and(juniper_warp::graphiql_filter("/graphql", None));

    warp::serve(graphiql_filter.or(warp::path("graphql").and(graphql_filter)))
        .run(([127, 0, 0, 1], 8080))
        .await
}

[tyranron]

@davidpdrsn but why do we need use raw arguments in proc macro tokens? The arguments are anyway wiil be named as a and b in schema. r#awing arguments is only required for usual Rust code, in proc macro we are free to use even keyword, so r#awing is not required.

[davidpdrsn]

In juniper-from-schema I use raw identifiers when generating code for all idents that come from the schema in case users put Rust keywords in the schema. I get that it isn't strictly necessary in this case but rather than checking if something is a keyword I would rather just use raw idents everywhere.