From bd5e232c1a1fd51cb0ba35172c41e76428819e5e Mon Sep 17 00:00:00 2001 From: Nicola Molinari Date: Tue, 6 Oct 2020 20:03:39 +0200 Subject: [PATCH] docs: keep old pages path but link to other documents --- .changeset/lemon-radios-travel.md | 2 +- website/src/content/deployment/http-server.mdx | 9 +++++++++ .../src/content/development/runtime-configuration.mdx | 9 +++++++++ website/src/content/main-concepts/graphql.mdx | 2 +- .../{migrating-apollo-v3.mdx => migrating-to-v17.mdx} | 9 +++------ 5 files changed, 23 insertions(+), 8 deletions(-) create mode 100644 website/src/content/deployment/http-server.mdx create mode 100644 website/src/content/development/runtime-configuration.mdx rename website/src/releases/2020-10/{migrating-apollo-v3.mdx => migrating-to-v17.mdx} (87%) diff --git a/.changeset/lemon-radios-travel.md b/.changeset/lemon-radios-travel.md index 6bfcb2fcd5..bc43700949 100644 --- a/.changeset/lemon-radios-travel.md +++ b/.changeset/lemon-radios-travel.md @@ -7,4 +7,4 @@ Migrate Apollo dependencies to `@apollo/client` package. -See full release notes: https://docs.commercetools.com/custom-applications/releases/2020-10-12-migrating-to-the-new-apollo-client-30 +See full release notes: https://docs.commercetools.com/custom-applications/releases/2020-10-12-migrating-to-v17 diff --git a/website/src/content/deployment/http-server.mdx b/website/src/content/deployment/http-server.mdx new file mode 100644 index 0000000000..ebf081629b --- /dev/null +++ b/website/src/content/deployment/http-server.mdx @@ -0,0 +1,9 @@ +--- +title: HTTP Server +--- + + + +As of `>= v17` this page no longer exists. Please refer to the [documentation about compiling a Custom Application](/deployment/compiling-a-custom-application) and the [release notes on how to replace the HTTP server](/releases/2020-10-12-migrating-to-v17). + + \ No newline at end of file diff --git a/website/src/content/development/runtime-configuration.mdx b/website/src/content/development/runtime-configuration.mdx new file mode 100644 index 0000000000..b1c10aa93e --- /dev/null +++ b/website/src/content/development/runtime-configuration.mdx @@ -0,0 +1,9 @@ +--- +title: Runtime Configuration +--- + + + +This page no longer exist. Please refer to the [documentation about the new application config](/development/application-config) and the [release notes on how to migrate to the new config](/releases/2020-07-16-introducing-a-new-and-simpler-application-config). + + \ No newline at end of file diff --git a/website/src/content/main-concepts/graphql.mdx b/website/src/content/main-concepts/graphql.mdx index a2506923eb..1edc74947b 100644 --- a/website/src/content/main-concepts/graphql.mdx +++ b/website/src/content/main-concepts/graphql.mdx @@ -31,4 +31,4 @@ Requests to the `/graphql` endpoint require one or more HTTP headers, to determi - `X-Project-Key` (_optional_): Specifies the project key to be used by the targeted GraphQL server. This value is not always required (depending on the query), but it's recommended to always send it whenever possible. -> As of version `>=17` of the `@commercetools-frontend/application-shell` package, it is recommended to use the `context` object to pass request metadata instead of the `variables` object. See related [release notes](https://docs.commercetools.com/custom-applications/releases/2020-10-12-migrating-to-the-new-apollo-client-30). +> As of version `>=17` of the `@commercetools-frontend/application-shell` package, it is recommended to use the `context` object to pass request metadata instead of the `variables` object. See related [release notes](/releases/2020-10-12-migrating-to-v17). diff --git a/website/src/releases/2020-10/migrating-apollo-v3.mdx b/website/src/releases/2020-10/migrating-to-v17.mdx similarity index 87% rename from website/src/releases/2020-10/migrating-apollo-v3.mdx rename to website/src/releases/2020-10/migrating-to-v17.mdx index 729f5eb16e..e012e298b4 100644 --- a/website/src/releases/2020-10/migrating-apollo-v3.mdx +++ b/website/src/releases/2020-10/migrating-to-v17.mdx @@ -1,9 +1,8 @@ --- date: 2020-10-12 -title: Migrating to the new Apollo Client 3.0 +title: Migrating to v17 description: | - With the new release of Apollo Client 3.0, certain breaking changes have been introduced which require some migration steps.\ - As a consequence, the Application Kit packages have also been released as a new major version v17.\ + The Application Kit packages have been released as a new major version v17.\ In this release note we go through the important migration steps. type: feature topics: @@ -11,9 +10,7 @@ topics: - Dependencies --- -With the new release of Apollo Client `3.0`, there are some important breaking changes which require some migration steps. See official migration guide https://www.apollographql.com/docs/react/migrating/apollo-client-3-migration/. - -As a consequence, the Application Kit packages have also been released as a new major version `v17`. +The Application Kit packages have been released as a new **major version** `v17`. One of the most important changes in this release relates to migrating to the new Apollo Client `v3`. See official migration guide https://www.apollographql.com/docs/react/migrating/apollo-client-3-migration/. Follow the steps below to migrate your Custom Application to the new versions.