diff --git a/guides/_sass/reset.scss b/guides/_sass/reset.scss
index ed11813c4e..47c6f90962 100644
--- a/guides/_sass/reset.scss
+++ b/guides/_sass/reset.scss
@@ -1,4 +1,4 @@
-/* http://meyerweb.com/eric/tools/css/reset/
+/* https://meyerweb.com/eric/tools/css/reset/
v2.0 | 20110126
License: none (public domain)
*/
diff --git a/guides/authorization/can_can_integration.md b/guides/authorization/can_can_integration.md
index 7e93f3bf28..ff7f4e295e 100644
--- a/guides/authorization/can_can_integration.md
+++ b/guides/authorization/can_can_integration.md
@@ -9,7 +9,7 @@ pro: true
---
-[GraphQL::Pro](http://graphql.pro) includes an integration for powering GraphQL authorization with [CanCan](https://github.com/CanCanCommunity/cancancan).
+[GraphQL::Pro](https://graphql.pro) includes an integration for powering GraphQL authorization with [CanCan](https://github.com/CanCanCommunity/cancancan).
__Why bother?__ You _could_ put your authorization code in your GraphQL types themselves, but writing a separate authorization layer gives you a few advantages:
diff --git a/guides/authorization/overview.md b/guides/authorization/overview.md
index e1b722cd54..61a40731b5 100644
--- a/guides/authorization/overview.md
+++ b/guides/authorization/overview.md
@@ -135,4 +135,4 @@ To accomplish these, you can use GraphQL-Ruby's authorization framework. The fra
- {% internal_link "Accessibility", "/authorization/accessibility" %} prevents running queries which access parts of the GraphQL schema, unless users have the required permission.
- {% internal_link "Authorization", "/authorization/authorization" %} checks application objects during execution to be sure the user has permission to access them.
-Also, [GraphQL::Pro](http://graphql.pro) has integrations for {% internal_link "CanCan", "/authorization/can_can_integration" %} and {% internal_link "Pundit", "/authorization/pundit_integration" %}.
+Also, [GraphQL::Pro](https://graphql.pro) has integrations for {% internal_link "CanCan", "/authorization/can_can_integration" %} and {% internal_link "Pundit", "/authorization/pundit_integration" %}.
diff --git a/guides/authorization/pundit_integration.md b/guides/authorization/pundit_integration.md
index 7162cc2844..1709bf7e04 100644
--- a/guides/authorization/pundit_integration.md
+++ b/guides/authorization/pundit_integration.md
@@ -8,7 +8,7 @@ index: 4
pro: true
---
-[GraphQL::Pro](http://graphql.pro) includes an integration for powering GraphQL authorization with [Pundit](https://github.com/varvet/pundit) policies.
+[GraphQL::Pro](https://graphql.pro) includes an integration for powering GraphQL authorization with [Pundit](https://github.com/varvet/pundit) policies.
__Why bother?__ You _could_ put your authorization code in your GraphQL types themselves, but writing a separate authorization layer gives you a few advantages:
diff --git a/guides/development.md b/guides/development.md
index 7c61fc589e..a8846b2dba 100644
--- a/guides/development.md
+++ b/guides/development.md
@@ -27,7 +27,7 @@ Then, install the dependencies:
- Install SQLite3 and MongoDB (eg, `brew install sqlite && brew install mongodb`)
- `bundle install`
-- Optional: [Ragel](http://www.colm.net/open-source/ragel/) is required to build the lexer
+- Optional: [Ragel](https://www.colm.net/open-source/ragel/) is required to build the lexer
### Running the Tests
@@ -121,7 +121,7 @@ BUNDLE_GEMFILE=gemfiles/rails_5.gemfile bundle exec rake
### Debugging with Pry
-[`pry`](http://pryrepl.org/) is included with GraphQL-Ruby's development setup to help with debugging.
+[`pry`](https://pryrepl.org/) is included with GraphQL-Ruby's development setup to help with debugging.
To pause execution in Ruby code, add:
@@ -224,7 +224,7 @@ Then, check them out locally:
```
$ bundle exec rake site:serve
-# then visit localhost:4000/api-doc/1.8.0/
+# then visit http://localhost:4000/api-doc/1.8.0/
```
Then, publish them as part of the whole site:
diff --git a/guides/errors/execution_errors.md b/guides/errors/execution_errors.md
index 12a94ca75d..f0613fc382 100644
--- a/guides/errors/execution_errors.md
+++ b/guides/errors/execution_errors.md
@@ -8,7 +8,7 @@ desc: The top-level "errors" array and how to use it.
index: 1
---
-The GraphQL specification [allows for a top-level `"errors"` key](http://facebook.github.io/graphql/October2016/#sec-Errors) in the response which may contain information about what went wrong during execution. For example:
+The GraphQL specification [allows for a top-level `"errors"` key](https://facebook.github.io/graphql/October2016/#sec-Errors) in the response which may contain information about what went wrong during execution. For example:
```ruby
{
@@ -62,7 +62,7 @@ When this error is raised, its `message` will be added to the `"errors"` key and
## Customizing Error JSON
-The default error JSON includes `"message"`, `"locations"` and `"path"`. The [forthcoming version](http://facebook.github.io/graphql/draft/#example-fce18) of the GraphQL spec recommends putting custom data in the `"extensions"` key of the error JSON.
+The default error JSON includes `"message"`, `"locations"` and `"path"`. The [forthcoming version](https://facebook.github.io/graphql/draft/#example-fce18) of the GraphQL spec recommends putting custom data in the `"extensions"` key of the error JSON.
You can customize this in two ways:
diff --git a/guides/getting_started.md b/guides/getting_started.md
index 895a77c81d..6160a1a679 100644
--- a/guides/getting_started.md
+++ b/guides/getting_started.md
@@ -41,7 +41,7 @@ Or, you can build a GraphQL server by hand:
### Declare types
-Types describe objects in your application and form the basis for [GraphQL's type system](http://graphql.org/learn/schema/#type-system).
+Types describe objects in your application and form the basis for [GraphQL's type system](https://graphql.org/learn/schema/#type-system).
```ruby
# app/graphql/types/post_type.rb
@@ -66,7 +66,7 @@ end
### Build a Schema
-Before building a schema, you have to define an [entry point to your system, the "query root"](http://graphql.org/learn/schema/#the-query-and-mutation-types):
+Before building a schema, you have to define an [entry point to your system, the "query root"](https://graphql.org/learn/schema/#the-query-and-mutation-types):
```ruby
class QueryType < GraphQL::Schema::Object
@@ -124,14 +124,14 @@ See {% internal_link "Executing Queries","/queries/executing_queries" %} for mor
## Use with Relay
-If you're building a backend for [Relay](http://facebook.github.io/relay/), you'll need:
+If you're building a backend for [Relay](https://facebook.github.io/relay/), you'll need:
- A JSON dump of the schema, which you can get by sending [`GraphQL::Introspection::INTROSPECTION_QUERY`](https://github.com/rmosolgo/graphql-ruby/blob/master/lib/graphql/introspection/introspection_query.rb)
- Relay-specific helpers for GraphQL, see the `GraphQL::Relay` guides.
## Use with Apollo Client
-[Apollo Client](http://dev.apollodata.com/) is a full featured, simple to use GraphQL client with convenient integrations for popular view layers. You don't need to do anything special to connect Apollo Client to a `graphql-ruby` server.
+[Apollo Client](https://www.apollographql.com/) is a full featured, simple to use GraphQL client with convenient integrations for popular view layers. You don't need to do anything special to connect Apollo Client to a `graphql-ruby` server.
## Use with GraphQL.js Client
diff --git a/guides/index.html b/guides/index.html
index 81a9248b24..249d13fe28 100644
--- a/guides/index.html
+++ b/guides/index.html
@@ -20,7 +20,7 @@
diff --git a/guides/javascript_client/overview.md b/guides/javascript_client/overview.md
index 100e3faaa3..ca88c15079 100644
--- a/guides/javascript_client/overview.md
+++ b/guides/javascript_client/overview.md
@@ -21,7 +21,7 @@ The source code is [in the graphql-ruby repository](https://github.com/rmosolgo/
See detailed guides for more info about its features:
-- {% internal_link "sync CLI", "javascript_client/sync" %} for use with [graphql-pro](http://graphql.pro)'s persisted query backend
+- {% internal_link "sync CLI", "javascript_client/sync" %} for use with [graphql-pro](https://graphql.pro)'s persisted query backend
- Subscription support:
- {% internal_link "Apollo integration", "/javascript_client/apollo_subscriptions" %}
- {% internal_link "Relay integration", "/javascript_client/relay_subscriptions" %}
diff --git a/guides/javascript_client/sync.md b/guides/javascript_client/sync.md
index 5a9a8a638a..26ee8abff9 100644
--- a/guides/javascript_client/sync.md
+++ b/guides/javascript_client/sync.md
@@ -8,7 +8,7 @@ desc: Javascript tooling for persisted queries with GraphQL-Ruby
index: 1
---
-JavaScript support for GraphQL projects using [graphql-pro](http://graphql.pro)'s `OperationStore` for persisted queries.
+JavaScript support for GraphQL projects using [graphql-pro](https://graphql.pro)'s `OperationStore` for persisted queries.
- [`sync` CLI](#sync-utility)
- [Relay support](#use-with-relay)
diff --git a/guides/pro/dashboard.md b/guides/pro/dashboard.md
index baaa73ed8b..638ebcb14c 100644
--- a/guides/pro/dashboard.md
+++ b/guides/pro/dashboard.md
@@ -10,7 +10,7 @@ pro: true
---
-[GraphQL-Pro](http://graphql-pro) includes a web dashboard for monitoring {% internal_link "Operation Store", "/operation_store/overview" %} and {% internal_link "subscriptions", "/subscriptions/pusher_implementation" %}.
+[GraphQL-Pro](https://graphql.pro) includes a web dashboard for monitoring {% internal_link "Operation Store", "/operation_store/overview" %} and {% internal_link "subscriptions", "/subscriptions/pusher_implementation" %}.
@@ -42,7 +42,7 @@ You should only allow admin users to see `/graphql/dashboard` because it allows
### Rails Routing Constraints
-Use [Rails routing constraints](http://api.rubyonrails.org/v5.1/classes/ActionDispatch/Routing/Mapper/Scoping.html#method-i-constraints) to restrict access to authorized users, for example:
+Use [Rails routing constraints](https://api.rubyonrails.org/v5.1/classes/ActionDispatch/Routing/Mapper/Scoping.html#method-i-constraints) to restrict access to authorized users, for example:
```ruby
# Check the secure session for a staff flag:
diff --git a/guides/pro/home.md b/guides/pro/home.md
index caa8eba89a..ad063c209c 100644
--- a/guides/pro/home.md
+++ b/guides/pro/home.md
@@ -1,7 +1,7 @@
---
layout: guide
doc_stub: false
-outbound_url: http://graphql.pro
+outbound_url: https://graphql.pro
title: GraphQL::Pro Home
section: GraphQL Pro
desc: Overview of GraphQL::Pro features
diff --git a/guides/queries/executing_queries.md b/guides/queries/executing_queries.md
index 56aae79689..2ec45f32cc 100644
--- a/guides/queries/executing_queries.md
+++ b/guides/queries/executing_queries.md
@@ -36,10 +36,10 @@ MySchema.multiplex([
There are also several options you can use:
-- `variables:` provides values for `$`-named [query variables](http://graphql.org/learn/queries/#variables)
+- `variables:` provides values for `$`-named [query variables](https://graphql.org/learn/queries/#variables)
- `context:` accepts application-specific data to pass to `resolve` functions
- `root_value:` will be provided to root-level `resolve` functions as `obj`
-- `operation_name:` picks a [named operation](http://graphql.org/learn/queries/#operation-name) from the incoming string to execute
+- `operation_name:` picks a [named operation](https://graphql.org/learn/queries/#operation-name) from the incoming string to execute
- `document:` accepts an already-parsed query (instead of a string), see {{ "GraphQL.parse" | api_doc }}
- `validate:` may be `false` to skip static validation for this query
- `max_depth:` and `max_complexity:` may override schema-level values
@@ -48,7 +48,7 @@ Some of these options are described in more detail below, see {{ "GraphQL::Query
## Variables
-GraphQL provides [query variables](http://graphql.org/learn/queries/#variables) as a way to parameterize query strings. If your query string contains variables, you can provide values in a hash of `{ String => value }` pairs. The keys should _not_ contain `"$"`.
+GraphQL provides [query variables](https://graphql.org/learn/queries/#variables) as a way to parameterize query strings. If your query string contains variables, you can provide values in a hash of `{ String => value }` pairs. The keys should _not_ contain `"$"`.
For example, to provide variables to a query:
diff --git a/guides/queries/multiplex.md b/guides/queries/multiplex.md
index bc9686e646..e3de25c249 100644
--- a/guides/queries/multiplex.md
+++ b/guides/queries/multiplex.md
@@ -8,7 +8,7 @@ desc: Run multiple queries concurrently
index: 10
---
-Some clients may send _several_ queries to the server at once (for example, [Apollo Client's query batching](http://dev.apollodata.com/core/network.html#query-batching)). You can execute them concurrently with {{ "Schema#multiplex" | api_doc }}.
+Some clients may send _several_ queries to the server at once (for example, [Apollo Client's query batching](https://www.apollographql.com/docs/react/advanced/network-layer.html#query-batching)). You can execute them concurrently with {{ "Schema#multiplex" | api_doc }}.
Multiplex runs have their own context, analyzers and instrumentation.
@@ -56,7 +56,7 @@ def execute
context = {}
# Apollo sends the params in a _json variable when batching is enabled
- # see the Apollo Documentation about query batching: http://dev.apollodata.com/core/network.html#query-batching
+ # see the Apollo Documentation about query batching: https://www.apollographql.com/docs/react/advanced/network-layer.html#query-batching
result = if params[:_json]
queries = params[:_json].map do |param|
{
diff --git a/guides/queries/timeout.md b/guides/queries/timeout.md
index 8fc0a6a06d..860158dc79 100644
--- a/guides/queries/timeout.md
+++ b/guides/queries/timeout.md
@@ -18,7 +18,7 @@ end
After `max_seconds`, no new fields will be resolved. Instead, errors will be added to the `errors` key for fields that weren't resolved.
-__Note__ that this _does not interrupt_ field execution (doing so is [buggy](http://www.mikeperham.com/2015/05/08/timeout-rubys-most-dangerous-api/)). If you're making external calls (eg, HTTP requests or database queries), make sure to use a library-specific timeout for that operation (eg, [Redis timeout](https://github.com/redis/redis-rb#timeouts), [Net::HTTP](https://ruby-doc.org/stdlib-2.4.1/libdoc/net/http/rdoc/Net/HTTP.html)'s `ssl_timeout`, `open_timeout`, and `read_timeout`).
+__Note__ that this _does not interrupt_ field execution (doing so is [buggy](https://www.mikeperham.com/2015/05/08/timeout-rubys-most-dangerous-api/)). If you're making external calls (eg, HTTP requests or database queries), make sure to use a library-specific timeout for that operation (eg, [Redis timeout](https://github.com/redis/redis-rb#timeouts), [Net::HTTP](https://ruby-doc.org/stdlib-2.4.1/libdoc/net/http/rdoc/Net/HTTP.html)'s `ssl_timeout`, `open_timeout`, and `read_timeout`).
To log the error, pass a block to the middleware:
diff --git a/guides/queries/tracing.md b/guides/queries/tracing.md
index 9ba0fc2e60..22301d7308 100644
--- a/guides/queries/tracing.md
+++ b/guides/queries/tracing.md
@@ -113,7 +113,7 @@ end
## Skylight
-To add [Skylight](http://skylight.io) instrumentation:
+To add [Skylight](https://www.skylight.io) instrumentation:
```ruby
class MySchema < GraphQL::Schema
diff --git a/guides/related_projects.md b/guides/related_projects.md
index 2d8ef22b94..0464ce1d17 100644
--- a/guides/related_projects.md
+++ b/guides/related_projects.md
@@ -11,7 +11,7 @@ Want to add something? Please open a pull request [on GitHub](https://github.com
## Code
-- `graphql-ruby` + Rails demo ([src](https://github.com/rmosolgo/graphql-ruby-demo) / [heroku](http://graphql-ruby-demo.herokuapp.com))
+- `graphql-ruby` + Rails demo ([src](https://github.com/rmosolgo/graphql-ruby-demo) / [heroku](https://graphql-ruby-demo.herokuapp.com))
- `graphql-ruby` + Sinatra demo ([src](https://github.com/robinjmurphy/ruby-graphql-server-example) / [heroku](https://ruby-graphql-server-example.herokuapp.com/))
- [`graphql-batch`](https://github.com/shopify/graphql-batch), a batched query execution strategy
- [`graphql-cache`](https://github.com/stackshareio/graphql-cache), a resolver-level caching solution
@@ -24,7 +24,6 @@ Want to add something? Please open a pull request [on GitHub](https://github.com
- [`graphql-query-resolver`](https://github.com/nettofarah/graphql-query-resolver), a graphql-ruby add-on to minimize N+1 queries.
- [`graphql-rails_logger`](https://github.com/jetruby/graphql-rails_logger), a logger which allows you to inspect GraphQL queries in a more readable format.
- [`apollo_upload_server-ruby`](https://github.com/jetruby/apollo_upload_server-ruby), a middleware which allows you to upload files with GraphQL and multipart/form-data using [`apollo-upload-client`](https://github.com/jaydenseric/apollo-upload-client) library on front-end.
-- [optics-agent-ruby](https://github.com/apollostack/optics-agent-ruby), a graphql-ruby agent for use with the [Apollo Optics](http://www.apollodata.com/optics) GraphQL performance tool.
- [`search_object_graphql`](https://github.com/rstankov/SearchObjectGraphQL), a DSL for defining search resolvers for GraphQL.
## Blog Posts
diff --git a/guides/schema/definition.md b/guides/schema/definition.md
index ffc656898b..0770d9ae20 100644
--- a/guides/schema/definition.md
+++ b/guides/schema/definition.md
@@ -47,7 +47,7 @@ There are lots of schema configuration options:
A GraphQL schema is a web of interconnected types, and it has a few starting points for discovering the elements of that web:
-__Root types__ (`query`, `mutation`, and `subscription`) are the [entry points for queries to the system](http://graphql.org/learn/schema/#the-query-and-mutation-types). Each one is an object type which can be connected to the schema by a method with the same name:
+__Root types__ (`query`, `mutation`, and `subscription`) are the [entry points for queries to the system](https://graphql.org/learn/schema/#the-query-and-mutation-types). Each one is an object type which can be connected to the schema by a method with the same name:
```ruby
class MySchema < GraphQL::Schema
diff --git a/guides/schema/introspection.md b/guides/schema/introspection.md
index d84b5b9390..d3c1760ca7 100644
--- a/guides/schema/introspection.md
+++ b/guides/schema/introspection.md
@@ -9,7 +9,7 @@ class_based_api: true
index: 2
---
-A GraphQL schema has a [built-in introspection system](http://graphql.org/learn/introspection/) that publishes the schema's structure. In fact, the introspection system can be queried using GraphQL, for example:
+A GraphQL schema has a [built-in introspection system](https://graphql.org/learn/introspection/) that publishes the schema's structure. In fact, the introspection system can be queried using GraphQL, for example:
```graphql
{
diff --git a/guides/schema/root_types.md b/guides/schema/root_types.md
index f25878f625..b8e99acb01 100644
--- a/guides/schema/root_types.md
+++ b/guides/schema/root_types.md
@@ -7,7 +7,7 @@ title: Root Types
desc: Root types are the entry points for queries, mutations and subscriptions.
---
-GraphQL queries begin from [root types](http://graphql.org/learn/schema/#the-query-and-mutation-types): `query`, `mutation`, and `subscription` (experimental).
+GraphQL queries begin from [root types](https://graphql.org/learn/schema/#the-query-and-mutation-types): `query`, `mutation`, and `subscription` (experimental).
Attach these to your schema using methods with the same name:
diff --git a/guides/subscriptions/ably_implementation.md b/guides/subscriptions/ably_implementation.md
index 36b4015966..f77b4e5b19 100644
--- a/guides/subscriptions/ably_implementation.md
+++ b/guides/subscriptions/ably_implementation.md
@@ -9,7 +9,7 @@ index: 7
pro: true
---
-[GraphQL Pro](http://graphql.pro) includes a subscription system based on [Redis](http://redis.io) and [Ably](http://ably.io) which works with any Ruby web framework.
+[GraphQL Pro](https://graphql.pro) includes a subscription system based on [Redis](https://redis.io) and [Ably](https://ably.io) which works with any Ruby web framework.
After creating an app on Ably, you can hook it up to your GraphQL schema.
@@ -95,7 +95,7 @@ appendonly yes
Otherwise, Redis will drop data that doesn't fit in memory (read more in ["Redis persistence"](https://redis.io/topics/persistence)).
-If you're already using Redis in your application, see ["Storing Data in Redis"](http://www.mikeperham.com/2015/09/24/storing-data-with-redis/) for options to isolate data and tune your configuration.
+If you're already using Redis in your application, see ["Storing Data in Redis"](https://www.mikeperham.com/2015/09/24/storing-data-with-redis/) for options to isolate data and tune your configuration.
## Schema configuration
diff --git a/guides/subscriptions/action_cable_implementation.md b/guides/subscriptions/action_cable_implementation.md
index 5a60ba2c89..03e663d523 100644
--- a/guides/subscriptions/action_cable_implementation.md
+++ b/guides/subscriptions/action_cable_implementation.md
@@ -8,7 +8,7 @@ desc: GraphQL subscriptions over ActionCable
index: 4
---
-[ActionCable](http://guides.rubyonrails.org/action_cable_overview.html) is a great platform for delivering GraphQL subscriptions on Rails 5+. It handles message passing (via `broadcast`) and transport (via `transmit` over a websocket).
+[ActionCable](https://guides.rubyonrails.org/action_cable_overview.html) is a great platform for delivering GraphQL subscriptions on Rails 5+. It handles message passing (via `broadcast`) and transport (via `transmit` over a websocket).
To get started, see examples in the API docs: {{ "GraphQL::Subscriptions::ActionCableSubscriptions" | api_doc }}.
diff --git a/guides/subscriptions/pusher_implementation.md b/guides/subscriptions/pusher_implementation.md
index 4050d9434b..e8347c73ee 100644
--- a/guides/subscriptions/pusher_implementation.md
+++ b/guides/subscriptions/pusher_implementation.md
@@ -9,7 +9,7 @@ index: 6
pro: true
---
-[GraphQL Pro](http://graphql.pro) includes a subscription system based on [Redis](http://redis.io) and [Pusher](http://pusher.com) which works with any Ruby web framework.
+[GraphQL Pro](https://graphql.pro) includes a subscription system based on [Redis](https://redis.io) and [Pusher](https://pusher.com) which works with any Ruby web framework.
After creating an app on Pusher and [configuring the Ruby gem](https://github.com/pusher/pusher-http-ruby#global), you can hook it up to your GraphQL schema.
@@ -86,7 +86,7 @@ appendonly yes
Otherwise, Redis will drop data that doesn't fit in memory (read more in ["Redis persistence"](https://redis.io/topics/persistence)).
-If you're already using Redis in your application, see ["Storing Data in Redis"](http://www.mikeperham.com/2015/09/24/storing-data-with-redis/) for options to isolate data and tune your configuration.
+If you're already using Redis in your application, see ["Storing Data in Redis"](https://www.mikeperham.com/2015/09/24/storing-data-with-redis/) for options to isolate data and tune your configuration.
## Schema configuration
diff --git a/guides/type_definitions/enums.md b/guides/type_definitions/enums.md
index 3b05ef5e5c..ee50973d67 100644
--- a/guides/type_definitions/enums.md
+++ b/guides/type_definitions/enums.md
@@ -9,7 +9,7 @@ index: 2
class_based_api: true
---
-Enum types are sets of discrete values. An enum field must return one of the possible values of the enum. In the [GraphQL Schema Definition Language](http://graphql.org/learn/schema/#type-language) (SDL), enums are described like this:
+Enum types are sets of discrete values. An enum field must return one of the possible values of the enum. In the [GraphQL Schema Definition Language](https://graphql.org/learn/schema/#type-language) (SDL), enums are described like this:
```ruby
enum MediaCategory {
@@ -20,7 +20,7 @@ enum MediaCategory {
}
```
-So, a `MediaCategory` value is one of: `AUDIO`, `IMAGE`, `TEXT`, or `VIDEO`. This is similar to [ActiveRecord enums](http://api.rubyonrails.org/classes/ActiveRecord/Enum.html).
+So, a `MediaCategory` value is one of: `AUDIO`, `IMAGE`, `TEXT`, or `VIDEO`. This is similar to [ActiveRecord enums](https://api.rubyonrails.org/classes/ActiveRecord/Enum.html).
In a GraphQL query, enums are written as identifiers (not strings), for example:
diff --git a/guides/type_definitions/input_objects.md b/guides/type_definitions/input_objects.md
index b31608912e..8ee65e7e48 100644
--- a/guides/type_definitions/input_objects.md
+++ b/guides/type_definitions/input_objects.md
@@ -19,7 +19,7 @@ mutation {
}
```
-Like a Ruby `Hash`, an input object consists of keys and values. Unlike a Hash, its keys and value types must be defined statically, as part of the GraphQL system. For example, here's an input object, expressed in the [GraphQL Schema Definition Language](http://graphql.org/learn/schema/#type-language) (SDL):
+Like a Ruby `Hash`, an input object consists of keys and values. Unlike a Hash, its keys and value types must be defined statically, as part of the GraphQL system. For example, here's an input object, expressed in the [GraphQL Schema Definition Language](https://graphql.org/learn/schema/#type-language) (SDL):
```ruby
input PostAttributes {
diff --git a/guides/type_definitions/interfaces.md b/guides/type_definitions/interfaces.md
index dfc2f5f18a..70480d3014 100644
--- a/guides/type_definitions/interfaces.md
+++ b/guides/type_definitions/interfaces.md
@@ -15,7 +15,7 @@ Interfaces are lists of fields which may be implemented by object types.
An interface has fields, but it's never actually instantiated. Instead, objects may _implement_ interfaces, which makes them a _member_ of that interface. Also, fields may _return_ interface types. When this happens, the returned object may be any member of that interface.
-For example, let's say a `Customer` (interface) may be either an `Individual` (object) or a `Company` (object). Here's the structure in the [GraphQL Schema Definition Language](http://graphql.org/learn/schema/#type-language) (SDL):
+For example, let's say a `Customer` (interface) may be either an `Individual` (object) or a `Company` (object). Here's the structure in the [GraphQL Schema Definition Language](https://graphql.org/learn/schema/#type-language) (SDL):
```graphql
interface Customer {
diff --git a/guides/type_definitions/lists.md b/guides/type_definitions/lists.md
index 40987d0829..69a6babda0 100644
--- a/guides/type_definitions/lists.md
+++ b/guides/type_definitions/lists.md
@@ -9,7 +9,7 @@ index: 6
class_based_api: true
---
-GraphQL has _list types_ which are ordered lists containing items of other types. The following examples use the [GraphQL Schema Definition Language](http://graphql.org/learn/schema/#type-language) (SDL).
+GraphQL has _list types_ which are ordered lists containing items of other types. The following examples use the [GraphQL Schema Definition Language](https://graphql.org/learn/schema/#type-language) (SDL).
Fields may return a single scalar value (eg `String`), or a _list_ of scalar values (eg, `[String]`, a list of strings):
diff --git a/guides/type_definitions/non_nulls.md b/guides/type_definitions/non_nulls.md
index 5450175f7b..5824db17c5 100644
--- a/guides/type_definitions/non_nulls.md
+++ b/guides/type_definitions/non_nulls.md
@@ -9,7 +9,7 @@ index: 7
class_based_api: true
---
-GraphQL's concept of _non-null_ is expressed in the [Schema Definition Language](http://graphql.org/learn/schema/#type-language) (SDL) with `!`, for example:
+GraphQL's concept of _non-null_ is expressed in the [Schema Definition Language](https://graphql.org/learn/schema/#type-language) (SDL) with `!`, for example:
```graphql
type User {
diff --git a/guides/type_definitions/objects.md b/guides/type_definitions/objects.md
index 8563a104a9..75d2db046a 100644
--- a/guides/type_definitions/objects.md
+++ b/guides/type_definitions/objects.md
@@ -29,7 +29,7 @@ And get back values like this:
}
```
-Generally speaking, GraphQL object types correspond to models in your application, like `User`, `Product`, or `Comment`. Sometimes, object types are described using the [GraphQL Schema Definition Language](http://graphql.org/learn/schema/#type-language) (SDL):
+Generally speaking, GraphQL object types correspond to models in your application, like `User`, `Product`, or `Comment`. Sometimes, object types are described using the [GraphQL Schema Definition Language](https://graphql.org/learn/schema/#type-language) (SDL):
```ruby
type User {
@@ -55,11 +55,11 @@ class User < GraphQL::Schema::Object
end
```
-The rest of this guide will describe how to define GraphQL object types in Ruby. To learn more about GraphQL object types in general, see the [GraphQL docs](http://graphql.org/learn/schema/#object-types-and-fields).
+The rest of this guide will describe how to define GraphQL object types in Ruby. To learn more about GraphQL object types in general, see the [GraphQL docs](https://graphql.org/learn/schema/#object-types-and-fields).
## Object classes
-Classes extending {{ "GraphQL::Schema::Object" | api_doc }} describe [Object types](http://graphql.org/learn/schema/#object-types-and-fields) and customize their behavior.
+Classes extending {{ "GraphQL::Schema::Object" | api_doc }} describe [Object types](https://graphql.org/learn/schema/#object-types-and-fields) and customize their behavior.
Object fields can be created with the `field(...)` class method, [described in detail below](#fields)
diff --git a/guides/type_definitions/scalars.md b/guides/type_definitions/scalars.md
index 73d6d32917..91c649fef1 100644
--- a/guides/type_definitions/scalars.md
+++ b/guides/type_definitions/scalars.md
@@ -44,7 +44,7 @@ Custom scalars (see below) can also be used by name:
field :homepage, Types::Url, null: true
```
-In the [Schema Definition Language](http://graphql.org/learn/schema/#type-language) (SDL), scalars are simply named:
+In the [Schema Definition Language](https://graphql.org/learn/schema/#type-language) (SDL), scalars are simply named:
```ruby
scalar DateTime
diff --git a/guides/type_definitions/unions.md b/guides/type_definitions/unions.md
index fda52f8fb7..06a8ec8f29 100644
--- a/guides/type_definitions/unions.md
+++ b/guides/type_definitions/unions.md
@@ -9,7 +9,7 @@ index: 5
class_based_api: true
---
-A union type is a set of object types which may appear in the same spot. Here's a union, expressed in [GraphQL Schema Definition Language](http://graphql.org/learn/schema/#type-language) (SDL):
+A union type is a set of object types which may appear in the same spot. Here's a union, expressed in [GraphQL Schema Definition Language](https://graphql.org/learn/schema/#type-language) (SDL):
```ruby
union MediaItem = AudioClip | VideoClip | Image | TextSnippet
diff --git a/javascript_client/LICENSE.md b/javascript_client/LICENSE.md
index 689a89046a..49e2d7a2d5 100644
--- a/javascript_client/LICENSE.md
+++ b/javascript_client/LICENSE.md
@@ -1,10 +1,10 @@
Copyright (c) Minimum Viable Software
`graphql-ruby-client` is an Open Source project licensed under the terms of
-the LGPLv3 license. Please see http://www.gnu.org/licenses/lgpl-3.0.html
+the LGPLv3 license. Please see https://www.gnu.org/licenses/lgpl-3.0.html
for license text.
`GraphQL::Pro` customers are granted a commercial-friendly license
allowing private forks and modifications of `graphql-ruby-client`.
-Please see http://graphql.pro/ for more detail. You can find the
-commercial license terms at http://graphql.pro/COMM-LICENSE.html.
+Please see https://graphql.pro/ for more detail. You can find the
+commercial license terms at https://graphql.pro/COMM-LICENSE.html.
diff --git a/javascript_client/readme.md b/javascript_client/readme.md
index 6a9ea3e2a8..30bb22d9f4 100644
--- a/javascript_client/readme.md
+++ b/javascript_client/readme.md
@@ -1,4 +1,4 @@
-Find the `graphql-ruby-client` docs on the [GraphQL-Ruby website](http://graphql-ruby.org/javascript_client/overview).
+Find the `graphql-ruby-client` docs on the [GraphQL-Ruby website](https://graphql-ruby.org/javascript_client/overview).
## License
diff --git a/lib/graphql/types/float.rb b/lib/graphql/types/float.rb
index 6fb646d330..7551899ed5 100644
--- a/lib/graphql/types/float.rb
+++ b/lib/graphql/types/float.rb
@@ -3,7 +3,7 @@
module GraphQL
module Types
class Float < GraphQL::Schema::Scalar
- description "Represents signed double-precision fractional values as specified by [IEEE 754](http://en.wikipedia.org/wiki/IEEE_floating_point)."
+ description "Represents signed double-precision fractional values as specified by [IEEE 754](https://en.wikipedia.org/wiki/IEEE_floating_point)."
def self.coerce_input(value, _ctx)
value.is_a?(Numeric) ? value.to_f : nil
diff --git a/readme.md b/readme.md
index e20ab6224a..7785ddb620 100644
--- a/readme.md
+++ b/readme.md
@@ -4,12 +4,12 @@
[![Gem Version](https://badge.fury.io/rb/graphql.svg)](https://rubygems.org/gems/graphql)
[![Code Climate](https://codeclimate.com/github/rmosolgo/graphql-ruby/badges/gpa.svg)](https://codeclimate.com/github/rmosolgo/graphql-ruby)
[![Test Coverage](https://codeclimate.com/github/rmosolgo/graphql-ruby/badges/coverage.svg)](https://codeclimate.com/github/rmosolgo/graphql-ruby)
-[![built with love](https://cloud.githubusercontent.com/assets/2231765/6766607/d07992c6-cfc9-11e4-813f-d9240714dd50.png)](http://rmosolgo.github.io/react-badges/)
+[![built with love](https://cloud.githubusercontent.com/assets/2231765/6766607/d07992c6-cfc9-11e4-813f-d9240714dd50.png)](https://rmosolgo.github.io/react-badges/)
-A Ruby implementation of [GraphQL](http://graphql.org/).
+A Ruby implementation of [GraphQL](https://graphql.org/).
-- [Website](https://rmosolgo.github.io/graphql-ruby)
-- [API Documentation](http://www.rubydoc.info/gems/graphql)
+- [Website](https://graphql-ruby.org/)
+- [API Documentation](https://www.rubydoc.info/gems/graphql)
- [Newsletter](https://tinyletter.com/graphql-ruby)
## Installation
@@ -33,11 +33,11 @@ $ rails generate graphql:install
After this, you may need to run `bundle install` again, as by default graphiql-rails is added on installation.
-Or, see ["Getting Started"](https://rmosolgo.github.io/graphql-ruby/).
+Or, see ["Getting Started"](https://graphql-ruby.org/).
## Upgrade
-I also sell [GraphQL::Pro](http://graphql.pro) which provides several features on top of the GraphQL runtime, including [Pundit authorization](http://rmosolgo.github.io/graphql-ruby/authorization/pundit_integration), [CanCan authorization](http://rmosolgo.github.io/graphql-ruby/authorization/can_can_integration), [Pusher-based subscriptions](http://graphql-ruby.org/subscriptions/pusher_implementation) and [persisted queries](http://rmosolgo.github.io/graphql-ruby/operation_store/overview). Besides that, Pro customers get email support and an opportunity to support graphql-ruby's development!
+I also sell [GraphQL::Pro](https://graphql.pro) which provides several features on top of the GraphQL runtime, including [Pundit authorization](https://graphql-ruby.org/authorization/pundit_integration), [CanCan authorization](https://graphql-ruby.org/authorization/can_can_integration), [Pusher-based subscriptions](https://graphql-ruby.org/subscriptions/pusher_implementation) and [persisted queries](https://graphql-ruby.org/operation_store/overview). Besides that, Pro customers get email support and an opportunity to support graphql-ruby's development!
## Goals
@@ -49,4 +49,4 @@ I also sell [GraphQL::Pro](http://graphql.pro) which provides several features o
- __Say hi & ask questions__ in the [#ruby channel on Slack](https://graphql-slack.herokuapp.com/) or [on Twitter](https://twitter.com/rmosolgo)!
- __Report bugs__ by posting a description, full stack trace, and all relevant code in a [GitHub issue](https://github.com/rmosolgo/graphql-ruby/issues).
-- __Start hacking__ with the [Development guide](http://graphql-ruby.org/development).
+- __Start hacking__ with the [Development guide](https://graphql-ruby.org/development).
diff --git a/spec/dummy/config/locales/en.yml b/spec/dummy/config/locales/en.yml
index decc5a8573..cf9b342d0a 100644
--- a/spec/dummy/config/locales/en.yml
+++ b/spec/dummy/config/locales/en.yml
@@ -27,7 +27,7 @@
# 'true': 'foo'
#
# To learn more, please read the Rails Internationalization guide
-# available at http://guides.rubyonrails.org/i18n.html.
+# available at https://guides.rubyonrails.org/i18n.html.
en:
hello: "Hello world"
diff --git a/spec/graphql/language/document_from_schema_definition_spec.rb b/spec/graphql/language/document_from_schema_definition_spec.rb
index 5dd4c40302..4ca1d96118 100644
--- a/spec/graphql/language/document_from_schema_definition_spec.rb
+++ b/spec/graphql/language/document_from_schema_definition_spec.rb
@@ -433,7 +433,7 @@
}
# Represents signed double-precision fractional values as specified by [IEEE
- # 754](http://en.wikipedia.org/wiki/IEEE_floating_point).
+ # 754](https://en.wikipedia.org/wiki/IEEE_floating_point).
scalar Float
# Represents a unique identifier that is Base64 obfuscated. It is often used to
@@ -698,7 +698,7 @@
}
# Represents signed double-precision fractional values as specified by [IEEE
- # 754](http://en.wikipedia.org/wiki/IEEE_floating_point).
+ # 754](https://en.wikipedia.org/wiki/IEEE_floating_point).
scalar Float
# Represents a unique identifier that is Base64 obfuscated. It is often used to