1972 - drafting @tag documentation. #1993
Conversation
|
@jeffjakub: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/ |
✅ Deploy Preview for apollo-federation-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
| directive @tag(from: String!) on FIELD_DEFINITION | INTERFACE | OBJECT | UNION | ARGUMENT_DEFINITION | SCALAR | ENUM | ENUM_VALUE | INPUT_OBJECT | INPUT_FIELD_DEFINITION | ||
| ``` | ||
|
|
||
| The `@tag` directive is used to provide a mechanism for applying arbitrary string metadata to the fields and types of a schema. This metadata is potentially useful throughout the schema’s lifecycle, including, but not limited to, processing, static analysis, and documentation. |
There was a problem hiding this comment.
should we also link to https://www.apollographql.com/docs/studio/contracts as that is the primary use case?
|
|
||
| ```graphql | ||
| schema | ||
| @core(feature: "https://specs.apollo.dev/core/v0.2") |
There was a problem hiding this comment.
should this be @linked instead? i.e. nowhere else in the docs we mention @core directive in our examples
|
|
||
| The `@tag` directive is used to provide a mechanism for applying arbitrary string metadata to the fields and types of a schema. This metadata is potentially useful throughout the schema’s lifecycle, including, but not limited to, processing, static analysis, and documentation. | ||
|
|
||
| ```graphql |
There was a problem hiding this comment.
I would add a sentence, saying that @tag will be propagated up to the supergraph automatically (as Phil mentioned in the @inaccessible spec)
Creating a draft PR to iterate on the
@tagdirective spec.This PR relates to: #1972