A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/graphql/graphql-spec/commit/f42dab54e9503abb027d52fd28c7745918143e90 below:

[Clarify] Note in Scalars about omittion from Schema. · graphql/graphql-spec@f42dab5 · GitHub

File tree Expand file treeCollapse file tree 1 file changed

+7

-0

lines changed

Filter options

Expand file treeCollapse file tree 1 file changed

+7

-0

lines changed Original file line number Diff line number Diff line change

@@ -80,6 +80,13 @@ client-specific primitive for time. Another example of a potentially useful

80 80

custom scalar is `Url`, which serializes as a string, but is guaranteed by

81 81

the server to be a valid URL.

82 82 83 +

A server may omit any of the built-in scalars from its schema, for example if a

84 +

schema does not refer to a floating-point number, then it will not include the

85 +

`Float` type. However, if a schema includes a type with the name of one of the

86 +

types described here, it must adhere to the behavior described. As an example,

87 +

a server must not include a type called `Int` and use it to represent

88 +

128-bit numbers, or internationalization information.

89 + 83 90

**Result Coercion**

84 91 85 92

A GraphQL server, when preparing a field of a given scalar type, must uphold the

You can’t perform that action at this time.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4