From 9ca07e7cb49dadc2949d7d49e6024cea204cdef4 Mon Sep 17 00:00:00 2001 From: Kei Kamikawa Date: Tue, 13 Apr 2021 01:28:32 +0900 Subject: [PATCH 1/4] fixed introspection field "specifiedBy" to "specifiedByURL" --- spec/Section 4 -- Introspection.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/spec/Section 4 -- Introspection.md b/spec/Section 4 -- Introspection.md index 42572ed9c..859b17c77 100644 --- a/spec/Section 4 -- Introspection.md +++ b/spec/Section 4 -- Introspection.md @@ -152,7 +152,7 @@ type __Type { ofType: __Type # should be non-null for custom SCALAR only, must be null for the others - specifiedBy: String + specifiedByURL: String } type __Field { @@ -242,13 +242,13 @@ actually valid. These kinds are listed in the `__TypeKind` enumeration. Represents scalar types such as Int, String, and Boolean. Scalars cannot have fields. Also represents [Custom scalars](#sec-Scalars.Custom-Scalars) which may provide -`specifiedBy` as a scalar specification URL. +`specifiedByURL` as a scalar specification URL. Fields * `kind` must return `__TypeKind.SCALAR`. * `name` must return a String. -* `specifiedBy` may return a String (in the form of a URL) for custom scalars, +* `specifiedByURL` may return a String (in the form of a URL) for custom scalars, otherwise must be {null}. * `description` may return a String or {null}. * All other fields must return {null}. From c414529d6d0bfe456bba0764a60496674b295a1f Mon Sep 17 00:00:00 2001 From: Kei Kamikawa Date: Tue, 13 Apr 2021 21:25:54 +0900 Subject: [PATCH 2/4] fixed specifiedBy to specifiedByURL in Section 3 --- spec/Section 3 -- Type System.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/spec/Section 3 -- Type System.md b/spec/Section 3 -- Type System.md index d4c77fb7f..a46fca95b 100644 --- a/spec/Section 3 -- Type System.md +++ b/spec/Section 3 -- Type System.md @@ -391,11 +391,11 @@ useful custom scalar is `URL`, which serializes as a string, but is guaranteed by the server to be a valid URL. When defining a custom scalar, GraphQL services should provide a specification -URL via the `@specifiedBy` directive or the `specifiedBy` introspection field. +URL via the `@specifiedBy` directive or the `specifiedByURL` introspection field. This URL must link to a human-readable specification of the data format, serialization, and coercion rules for the scalar. For example, a GraphQL service providing a `UUID` scalar may link to RFC 4122, or some custom document defining -a reasonable subset of that RFC. If a scalar `specifiedBy` URL is present, +a reasonable subset of that RFC. If a scalar `specifiedByURL` URL is present, systems and tools that are aware of it should conform to its described rules. ```graphql example @@ -411,7 +411,7 @@ Custom scalar specification URLs should not be changed once defined. Doing so would likely disrupt tooling or could introduce breaking changes within the linked specification's contents. -Built-in scalar types must not provide a `specifiedBy` URL as they are specified +Built-in scalar types must not provide a `specifiedByURL` URL as they are specified by this document. Note: Custom scalars should also summarize the specified format and provide From ae71c11033e71c4ac4802fcf7d320de0aea951fc Mon Sep 17 00:00:00 2001 From: Lee Byron Date: Fri, 16 Apr 2021 14:55:10 -0700 Subject: [PATCH 3/4] Remove redundant URL --- spec/Section 3 -- Type System.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/Section 3 -- Type System.md b/spec/Section 3 -- Type System.md index a46fca95b..44d23068a 100644 --- a/spec/Section 3 -- Type System.md +++ b/spec/Section 3 -- Type System.md @@ -395,7 +395,7 @@ URL via the `@specifiedBy` directive or the `specifiedByURL` introspection field This URL must link to a human-readable specification of the data format, serialization, and coercion rules for the scalar. For example, a GraphQL service providing a `UUID` scalar may link to RFC 4122, or some custom document defining -a reasonable subset of that RFC. If a scalar `specifiedByURL` URL is present, +a reasonable subset of that RFC. If a scalar `specifiedByURL` is present, systems and tools that are aware of it should conform to its described rules. ```graphql example @@ -411,7 +411,7 @@ Custom scalar specification URLs should not be changed once defined. Doing so would likely disrupt tooling or could introduce breaking changes within the linked specification's contents. -Built-in scalar types must not provide a `specifiedByURL` URL as they are specified +Built-in scalar types must not provide a `specifiedByURL` as they are specified by this document. Note: Custom scalars should also summarize the specified format and provide From 6b43350ea794602f246f77d68b5db2db890b5523 Mon Sep 17 00:00:00 2001 From: Lee Byron Date: Fri, 16 Apr 2021 14:58:30 -0700 Subject: [PATCH 4/4] use term --- spec/Section 3 -- Type System.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/Section 3 -- Type System.md b/spec/Section 3 -- Type System.md index 44d23068a..4b4da9661 100644 --- a/spec/Section 3 -- Type System.md +++ b/spec/Section 3 -- Type System.md @@ -395,7 +395,7 @@ URL via the `@specifiedBy` directive or the `specifiedByURL` introspection field This URL must link to a human-readable specification of the data format, serialization, and coercion rules for the scalar. For example, a GraphQL service providing a `UUID` scalar may link to RFC 4122, or some custom document defining -a reasonable subset of that RFC. If a scalar `specifiedByURL` is present, +a reasonable subset of that RFC. If a scalar specification URL is present, systems and tools that are aware of it should conform to its described rules. ```graphql example @@ -411,7 +411,7 @@ Custom scalar specification URLs should not be changed once defined. Doing so would likely disrupt tooling or could introduce breaking changes within the linked specification's contents. -Built-in scalar types must not provide a `specifiedByURL` as they are specified +Built-in scalar types must not provide a specification URL as they are specified by this document. Note: Custom scalars should also summarize the specified format and provide