kylefang/apollo
1
0
Fork 0
mirror of https://github.com/zhigang1992/apollo.git synced 2026-01-12 08:53:57 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix a bunch of broken links

Browse Source
This commit is contained in:
Stephen Barlow
2019-08-16 15:05:35 -07:00
parent 3b0a44fe0f
commit d49cea46d4
3 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/source/index.mdx
View File

@@ -11,13 +11,13 @@ It's easy to adopt Apollo incrementally, meaning you can set it up alongside an
**The Apollo platform consists of:**
- [Apollo Client](/react/), an open-source library for managing state in application clients
- [Apollo Client](https://apollographql.com/docs/react/), an open-source library for managing state in application clients
- [Apollo Server](/apollo-server), an open-source framework for implementing and running a data graph at scale
- [Apollo Server](https://apollographql.com/docs/apollo-server/), an open-source framework for implementing and running a data graph at scale
- [Apollo Graph Manager](/platform/graph-manager-overview) (formerly Engine), a cloud service that helps you manage, validate, and secure your organization's data graph
- [Apollo Graph Manager](https://apollographql.com/docs/platform/graph-manager-overview) (formerly Engine), a cloud service that helps you manage, validate, and secure your organization's data graph
- Developer tools that make it even easier to work with Apollo, including extensions for [Chrome](/react/features/developer-tooling/#apollo-client-devtools) and [VS Code](/platform/editor-plugins/)
- Developer tools that make it even easier to work with Apollo, including extensions for [Chrome](https://apollographql.com/docs/react/features/developer-tooling/#apollo-client-devtools) and [VS Code](/platform/editor-plugins/)
Conveniently, we have a tutorial that introduces you to each component of the platform. Ready to dive in?

4
docs/source/platform/graph-manager-overview.md
View File

@@ -131,7 +131,7 @@ You can delete a graph from Graph Manager by visiting its Settings page and clic
Every graph in Graph Manager should correspond to a single application. However, a single
application might run in multiple _environments_ (such as test, staging, and production).
To distinguish between graph activity for different application environments, you can define [**variants**](/platform/schema-registry.html#schema-tags) for a graph. Each variant has its own schema
To distinguish between graph activity for different application environments, you can define [**variants**](https://www.apollographql.com/docs/platform/schema-registry/#managing-environments) for a graph. Each variant has its own schema
that can (but doesn't have to) differ from the default variant.
When your server sends metrics to Graph Manager, it can associate an operation with
@@ -143,7 +143,7 @@ each application environment in isolation.
Graph Manager ingests and stores performance metrics data sent from your GraphQL server.
Use one of the following methods to send data to Graph Manager:
* Use [Apollo Server](/apollo-server/) as your application's GraphQL server and [include a Graph Manager API key](/tutorial/production/#get-an-engine-api-key) in your server configuration.
* Use [Apollo Server](https://www.apollographql.com/docs/apollo-server/) as your application's GraphQL server and [include a Graph Manager API key](/tutorial/production/#get-an-engine-api-key) in your server configuration.
* If you aren't using Apollo Server, you can send trace metrics to the [Graph Manager reporting endpoint](/references/setup-analytics/#engine-reporting-endpoint) (again,
providing an API key with every request).

10
docs/source/references/graph-manager-data-privacy.md
View File

@@ -45,7 +45,7 @@ Manager. The responses from your GraphQL service stay internal to your applicati
By default, if Apollo Server sees a response that includes an `errors` field, it reports the values
of the error's `message` and `locations` fields (if any) to Graph Manager.
You can use the [`rewriteError` reporting option](/apollo-server/api/apollo-server/#enginereportingoptions) to filter or transform errors before they're stored in
You can use the [`rewriteError` reporting option](https://www.apollographql.com/docs/apollo-server/api/apollo-server/#enginereportingoptions) to filter or transform errors before they're stored in
Graph Manager. Use this to strip sensitive data from errors or filter "safe" errors from Graph Manager reports.
### Query operation strings
@@ -61,7 +61,7 @@ as passwords or personally identifiable information) in operation strings**. Ins
In Apollo Server 2.7.0 and later, **none** of an
operation's GraphQL variables is sent to Graph Manager by default.
You can set a value for the [`sendVariableValues` reporting option](/apollo-server/api/apollo-server/#enginereportingoptions) to specify a different strategy for reporting
You can set a value for the [`sendVariableValues` reporting option](https://www.apollographql.com/docs/apollo-server/api/apollo-server/#enginereportingoptions) to specify a different strategy for reporting
some or all of your GraphQL variables.
#### Versions prior to 2.7.0
@@ -71,7 +71,7 @@ variables are sent to Graph Manager by default.
If you're using an earlier version of Apollo Server, it's recommended that you
update. If you can't update for whatever reason, you can use the
[`privateVariables` reporting option](/apollo-server/api/apollo-server/#enginereportingoptions)
[`privateVariables` reporting option](https://www.apollographql.com/docs/apollo-server/api/apollo-server/#enginereportingoptions)
to specify the names of variables that should _not_ be sent to Graph Manager. You
can also set this option to `false` to prevent all variables from being sent.
This reporting option is deprecated and will not be available in future versions of Apollo Server.
@@ -95,7 +95,7 @@ You can, however, configure reporting options for all other HTTP headers.
In Apollo Server 2.7.0 and later, **none** of an
operation's HTTP headers is sent to Graph Manager by default.
You can set a value for the [`sendHeaders` reporting option](/apollo-server/api/apollo-server/#enginereportingoptions) to specify a different strategy for reporting
You can set a value for the [`sendHeaders` reporting option](https://www.apollographql.com/docs/apollo-server/api/apollo-server/#enginereportingoptions) to specify a different strategy for reporting
some or all of your HTTP headers.
#### Versions prior to 2.7.0
@@ -105,7 +105,7 @@ In versions of Apollo Server 2 _prior_ to 2.7.0, **all** of an operation's HTTP
If you're using an earlier version of Apollo Server, it's recommended that you
update. If you can't update for
whatever reason, you can use the [`privateHeaders` reporting option](/apollo-server/api/apollo-server/#enginereportingoptions) to specify the names of variables
whatever reason, you can use the [`privateHeaders` reporting option](https://www.apollographql.com/docs/apollo-server/api/apollo-server/#enginereportingoptions) to specify the names of variables
that should _not_ be sent to Graph Manager. You can also set this
option to `false` to prevent all headers from being sent.
This reporting option is deprecated and will not be available in future versions of Apollo Server.