From a08ce0760d4122cea84162840c98093b2c3b12c0 Mon Sep 17 00:00:00 2001 From: Christian Legnitto Date: Tue, 23 Jun 2020 22:41:09 -1000 Subject: [PATCH] Add note about i64/u64 to the book Fixes https://github.com/graphql-rust/juniper/issues/671 --- docs/book/content/types/scalars.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/book/content/types/scalars.md b/docs/book/content/types/scalars.md index c2d9ca50..cafcfb99 100644 --- a/docs/book/content/types/scalars.md +++ b/docs/book/content/types/scalars.md @@ -27,6 +27,8 @@ Juniper has built-in support for: spec](http://facebook.github.io/graphql/#sec-ID) as a type that is serialized as a string but can be parsed from both a string and an integer. +Note that there is no built-in support for `i64`/`u64`, as the GraphQL spec [doesn't define any built-in scalars for `i64`/`u64` by default](https://spec.graphql.org/June2018/#sec-Int). You may wish to leverage a [custom GraphQL scalar](#custom-scalars) in your schema to support them. + **Third party types**: Juniper has built-in support for a few additional types from common third party