From 2abc0558d17cb950913a384f17d3d71eb457065b Mon Sep 17 00:00:00 2001 From: Maria Elisabeth Schreiber Date: Mon, 9 Sep 2024 09:56:43 -0600 Subject: [PATCH] Fix links --- src/content/basics/resources/faq.mdx | 2 +- src/content/graphos/delivery/check-configurations.mdx | 2 +- src/content/graphos/delivery/checks-reference.mdx | 2 +- .../graphos/delivery/schema-proposals/implementation.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/basics/resources/faq.mdx b/src/content/basics/resources/faq.mdx index 4a1fc18bb..c842889e0 100644 --- a/src/content/basics/resources/faq.mdx +++ b/src/content/basics/resources/faq.mdx @@ -197,6 +197,6 @@ Apollo Client comes with everything needed to test a client app that makes queri ### How can I safely make changes to my schema? -Schemas naturally evolve over time. GraphQL schemas are more resilient to change than other APIs, but there are still occasions where breaking changes are necessary to support new functionality. [This section](/graphos/delivery/schema-checks#types-of-schema-changes) explains in more detail which kinds of changes are always safe to make, and which kinds might break existing clients. +Schemas naturally evolve over time. GraphQL schemas are more resilient to change than other APIs, but there are still occasions where breaking changes are necessary to support new functionality. [This section](/graphos/delivery/checks-reference#types-of-schema-changes) explains in more detail which kinds of changes are always safe to make, and which kinds might break existing clients. The [schema checks](/graphos/delivery/schema-checks) feature of Apollo GraphOS helps you identify potentially breaking schema changes before you make them. diff --git a/src/content/graphos/delivery/check-configurations.mdx b/src/content/graphos/delivery/check-configurations.mdx index fff2f7a0c..bfb287492 100644 --- a/src/content/graphos/delivery/check-configurations.mdx +++ b/src/content/graphos/delivery/check-configurations.mdx @@ -91,7 +91,7 @@ Compared 1 schema changes against 24 operations View full details at https://studio.apollographql.com/service/docs-example-graph/checks/
``` -Each change to the schema is labeled either `PASS` or `FAIL`. For a complete list of schema change codes, see the [Reference](./checks-reference#schema-change-types). +Each change to the schema is labeled either `PASS` or `FAIL`. For a complete list of schema change codes, see the [Reference](./checks-reference#types-of-schema-changes). diff --git a/src/content/graphos/delivery/checks-reference.mdx b/src/content/graphos/delivery/checks-reference.mdx index c3c6e75ad..adf5d1cd3 100644 --- a/src/content/graphos/delivery/checks-reference.mdx +++ b/src/content/graphos/delivery/checks-reference.mdx @@ -87,7 +87,7 @@ A user has chosen to [ignore](#overriding-flagged-changes) schema change(s) for -## Schema change types +## Types of schema changes When you run a schema check, the check response classifies each schema change with the following codes. diff --git a/src/content/graphos/delivery/schema-proposals/implementation.mdx b/src/content/graphos/delivery/schema-proposals/implementation.mdx index c3f5e2538..a979821ae 100644 --- a/src/content/graphos/delivery/schema-proposals/implementation.mdx +++ b/src/content/graphos/delivery/schema-proposals/implementation.mdx @@ -32,7 +32,7 @@ A proposal's ID is always prefixed with `p-` and followed by a number. You can f ## Validate changes with checks -GraphOS provides [schema checks](../schema-checks) to help you identify breaking changes. You [run checks on local changes](../schema-checks#the-checks-lifecycle) before publishing them. +GraphOS provides [schema checks](../schema-checks) to help you identify breaking changes. You [run checks on local changes](../check-configurations#the-checks-lifecycle) before publishing them. Since schema checks [run automatically on every revision](./creation#schema-checks) in a proposal, if your last revision's checks pass, any changes you implement locally from a proposal should pass too. Regardless, it's best to run checks before publishing changes to make sure errors haven't crept in.