diff --git a/README.md b/README.md index daad91445..03f3febc0 100644 --- a/README.md +++ b/README.md @@ -1,14 +1,14 @@ # GraphQL The GraphQL specification is edited in the markdown files found in [`/spec`](./spec) -the latest release of which is published at http://facebook.github.io/graphql/. +the latest release of which is published at https://facebook.github.io/graphql/. -The latest draft specification can be found at http://facebook.github.io/graphql/draft/ +The latest draft specification can be found at https://facebook.github.io/graphql/draft/ which tracks the latest commit to the master branch in this repository. Previous releases of the GraphQL specification can be found at permalinks that match their [release tag](https://github.com/facebook/graphql/releases). For -example, http://facebook.github.io/graphql/October2016/. If you are linking +example, https://facebook.github.io/graphql/October2016/. If you are linking directly to the GraphQL specification, it's best to link to a tagged permalink for the particular referenced version. @@ -24,7 +24,7 @@ In order to be broadly adopted, GraphQL will have to target a wide variety of backends, frameworks, and languages, which will necessitate a collaborative effort across projects and organizations. This specification serves as a point of coordination for this effort. -Looking for help? Find resources [from the community](http://graphql.org/community/). +Looking for help? Find resources [from the community](https://graphql.org/community/). ## Getting Started diff --git a/spec/GraphQL.md b/spec/GraphQL.md index 8bde5176a..df1e74bc8 100644 --- a/spec/GraphQL.md +++ b/spec/GraphQL.md @@ -13,7 +13,7 @@ this open standard started in 2015. GraphQL has evolved and may continue to evolve in future editions of this specification. Previous editions of the GraphQL specification can be found at permalinks that match their [release tag](https://github.com/facebook/graphql/releases). -The latest working draft release can be found at [facebook.github.io/graphql/draft/](http://facebook.github.io/graphql/draft/). +The latest working draft release can be found at [facebook.github.io/graphql/draft/](https://facebook.github.io/graphql/draft/). **Copyright notice** diff --git a/spec/Section 2 -- Language.md b/spec/Section 2 -- Language.md index 012f19b08..f9f4c7669 100644 --- a/spec/Section 2 -- Language.md +++ b/spec/Section 2 -- Language.md @@ -19,7 +19,7 @@ used in this document. SourceCharacter :: /[\u0009\u000A\u000D\u0020-\uFFFF]/ GraphQL documents are expressed as a sequence of -[Unicode](http://unicode.org/standard/standard.html) characters. However, with +[Unicode](https://unicode.org/standard/standard.html) characters. However, with few exceptions, most of GraphQL is expressed only in the original non-control ASCII range so as to be as widely compatible with as many existing tools, languages, and serialization formats as possible and avoid display issues in diff --git a/spec/Section 3 -- Type System.md b/spec/Section 3 -- Type System.md index 00bbb8e49..770df75fa 100644 --- a/spec/Section 3 -- Type System.md +++ b/spec/Section 3 -- Type System.md @@ -179,7 +179,7 @@ made available via introspection. To allow GraphQL service designers to easily publish documentation alongside the capabilities of a GraphQL service, GraphQL descriptions are defined using the -Markdown syntax (as specified by [CommonMark](http://commonmark.org/)). In the +Markdown syntax (as specified by [CommonMark](https://commonmark.org/)). In the type system definition language, these description strings (often {BlockString}) occur immediately before the definition they describe. @@ -438,7 +438,7 @@ encoding integer numbers larger than 32-bit. ### Float The Float scalar type represents signed double-precision fractional values -as specified by [IEEE 754](http://en.wikipedia.org/wiki/IEEE_floating_point). +as specified by [IEEE 754](https://en.wikipedia.org/wiki/IEEE_floating_point). Response formats that support an appropriate double-precision number type should use that type to represent this scalar. @@ -517,7 +517,7 @@ often numeric, it should always serialize as a `String`. GraphQL is agnostic to ID format, and serializes to string to ensure consistency across many formats ID could represent, from small auto-increment numbers, to large 128-bit random numbers, to base64 encoded values, or string values of a -format like [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier). +format like [GUID](https://en.wikipedia.org/wiki/Globally_unique_identifier). GraphQL servers should coerce as appropriate given the ID formats they expect. When coercion is not possible they must raise a field error. @@ -1766,7 +1766,7 @@ to indicate deprecated portions of a GraphQL service's schema, such as deprecated fields on a type or deprecated enum values. Deprecations include a reason for why it is deprecated, which is formatted using -Markdown syntax (as specified by [CommonMark](http://commonmark.org/)). +Markdown syntax (as specified by [CommonMark](https://commonmark.org/)). In this example type definition, `oldField` is deprecated in favor of using `newField`. diff --git a/spec/Section 4 -- Introspection.md b/spec/Section 4 -- Introspection.md index 7990ae11a..8a24e2882 100644 --- a/spec/Section 4 -- Introspection.md +++ b/spec/Section 4 -- Introspection.md @@ -71,7 +71,7 @@ underscores. All types in the introspection system provide a `description` field of type `String` to allow type designers to publish documentation in addition to capabilities. A GraphQL server may return the `description` field using Markdown -syntax (as specified by [CommonMark](http://commonmark.org/)). Therefore it is +syntax (as specified by [CommonMark](https://commonmark.org/)). Therefore it is recommended that any tool that displays `description` use a CommonMark-compliant Markdown renderer.