kylefang/apollo
1
0
Fork 0
mirror of https://github.com/zhigang1992/apollo.git synced 2026-05-13 17:30:47 +08:00
Code Issues Packages Projects Releases Wiki Activity

Removing more Here links.

Browse Source 
Removed here links across all platform docs.
This commit is contained in:
adamatorres
2019-04-16 16:51:00 -07:00
parent 960082891c
commit 07e00f9055
4 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/source/platform/editor-plugins.md
View File

@@ -72,7 +72,7 @@ module.exports = {
> Linking to the local schema won't provide all features such as switching schema tags and performance metrics.
More information about configuring an Apollo project can be found [here](../platform/apollo-config.html)
Please see [Configuring Apollo Projects](https://www.apollographql.com/docs/references/apollo-config) for more information.
<h3 id="client-only-schemas">Client-only schemas</h3>
@@ -146,8 +146,7 @@ The Apollo GraphQL platform supports publishing multiple versions (tags) of a sc
<h2 id="troubleshooting">Troubleshooting</h2>
The most common errors are configuration errors, like a missing `.env` file or incorrect service information in the `apollo.config.js` file.
There is more information about configuring an Apollo projects [here](../platform/apollo-config.html).
The most common errors are configuration errors, like a missing `.env` file or incorrect service information in the `apollo.config.js` file. Please see [Configuring Apollo Projects](https://www.apollographql.com/docs/references/apollo-config) for more configuration guidance.
Other errors may be caused from an old version of a published schema. To reload a schema, open the Command Palette (`cmd + shift + p` on mac), search "Apollo" and choose the "Apollo: Reload Schema" option.

2
docs/source/platform/integrations.md
View File

@@ -62,7 +62,7 @@ jobs:
fi
```
> **Note:** Your `apollo service:check` command needs a source to from which to fetch your schema. This is most commonly provided as a URL to a running server (with introspection enabled), but can also be provided as a path to a file with your schema in it. See other options [here](/docs/platform/schema-registry.html#setup).
> **Note:** Your `apollo service:check` command needs a source to from which to fetch your schema. This is most commonly provided as a URL to a running server (with introspection enabled), but can also be provided as a path to a file with your schema in it. See [Using the Schema Registry](/docs/platform/schema-registry.html#setup) setup for other options.
The `apollo schema:check` command checks for differences in your schema between what's on your current branch and the last version you uploaded to Engine. If you've removed or changed any types or fields, it will validate that those changes won't break any of the queries that your clients have made recently. If your changes do break any queries, the check will fail.

2
docs/source/platform/schema-validation.md
View File

@@ -7,7 +7,7 @@ As GraphQL scales within an organization, it's important in schema evolution to
As such, schema change validation is one of the cornerstones of the [Apollo Platform](/docs/intro/platform.html) and we've built a set of tools to make the workflow possible.
> **Note:** Schema validation is an Apollo Platform feature available on the [_Team_ and _Enterprise_ plans](https://www.apollographql.com/plans/). To get started with the Apollo Platform, begin with [the documentation](https://www.apollographql.com/docs/). If you already have an Engine account, upgrade to a Team plan [here](https://engine.apollographql.com/trypro).
> **Note:** Schema validation is an Apollo Platform feature available on the [_Team_ and _Enterprise_ plans](https://www.apollographql.com/plans/). To get started with the Apollo Platform, begin with [the documentation](https://www.apollographql.com/docs/). If you already have an Engine account, upgrade to a [Team plan](https://engine.apollographql.com/trypro).
<h2 id="schema-validation">How it works</h2>

4
docs/source/platform/tracing.md
View File

@@ -79,7 +79,7 @@ becomes
query Foo{user(id:""){name timezone...Baz}}fragment Baz on User{dob}
```
> A reference implementation of query signatures is available [here](https://github.com/apollographql/apollo-server/blob/master/packages/apollo-engine-reporting/src/signature.ts).
> See the reference implementation of [query signatures](https://github.com/apollographql/apollo-tooling/blob/7e1f62a8635466e653d52064745bf8c66bb7dd10/packages/apollo-graphql/src/operationId.ts#L60) for more information.
<h3 id="signatures-sensitive-data">Signatures and sensitive data</h3>
@@ -91,4 +91,4 @@ But where possible, we strongly advise that you keep sensitive data in GraphQL v
<h2 id="tracking-subs">A note on GraphQL subscriptions</h2>
Engine does not currently track statistics or traces for subscriptions. The proxy does, however, support the transparent pass-through of subscription requests and responses.
Engine does not currently track statistics or traces for subscriptions. The proxy does, however, support the transparent pass-through of subscription requests and responses.