From 5608a0986981636485794b850314f6b6c8433893 Mon Sep 17 00:00:00 2001 From: Peter Kolloch Date: Wed, 23 Feb 2022 16:54:39 +0100 Subject: [PATCH] custom_scalars: i64 not encoded as string Remove the note that incorrectly claims that i64 are encoded as strings. Also see https://github.com/async-graphql/async-graphql/issues/196 --- docs/en/src/custom_scalars.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/src/custom_scalars.md b/docs/en/src/custom_scalars.md index 1a7fd6c1..dd16d438 100644 --- a/docs/en/src/custom_scalars.md +++ b/docs/en/src/custom_scalars.md @@ -4,7 +4,7 @@ In `Async-graphql` most common scalar types are built in, but you can also creat Using `async-graphql::Scalar`, you can add support for a scalar when you implement it. You only need to implement parsing and output functions. -The following example defines a 64-bit integer scalar where its input and output are strings. (Note: `Async-graphql` already supports 64-bit integers and uses strings as input and output.) +The following example defines a 64-bit integer scalar where its input and output are strings. ```rust use async_graphql::*;