-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release docs #389
Release docs #389
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking great!!
docs/source/supergraphs.md
Outdated
[data core]: https://apollo-specs.github.io/#def-data-core | ||
[referencing specifications]: https://apollo-specs.github.io/core/draft/pre-0#core__Using | ||
|
||
Currently, supergraph schemas are in preview, and can't be directly consumed by anything. In the future, a supergraph schema document will be consumable by [apollo gateway](https://www.apollographql.com/docs/federation/gateway/), providing all the information needed to execute operations against a supergraph. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, supergraph schemas are in preview, and can't be directly consumed by anything. In the future, a supergraph schema document will be consumable by [apollo gateway](https://www.apollographql.com/docs/federation/gateway/), providing all the information needed to execute operations against a supergraph. | |
Currently, supergraph schemas are in preview, and can't be directly consumed by anything. In the future, a supergraph schema document will be consumable by [Apollo gateway](https://www.apollographql.com/docs/federation/gateway/), providing all the information needed to execute operations against a supergraph. |
docs/source/supergraphs.md
Outdated
Rover's `supergraph compose` command provides all the tools you need to compose a supergraph's schema locally. | ||
|
||
```bash | ||
rover supergraph compose --config ./subgraphs.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rover supergraph compose --config ./subgraphs.yaml | |
rover supergraph compose --config ./supergraph.yaml |
docs/source/supergraphs.md
Outdated
|
||
The config format that `supergraph compose` expects is a slim YAML file, containing a list of subgraphs, their public facing urls to route requests to, and where Rover can find their schemas. | ||
|
||
Currently, **only federated SDL files are accepted for schema sources**. If you don't have a schema file for a subgraph, you can pipe the output of [`subgraph introspect`](./subgraphs#fetching-via-enhanced-introspection) to a file (see [using stdout](./essentials#using-stdout) for more). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could also reasonably pipe rover subgraph fetch
to a file if a subgraph already exists in the registry
docs/source/supergraphs.md
Outdated
films: | ||
routing_url: https://films.example.com | ||
schema: | ||
file: ./good-films.graphql |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
file: ./good-films.graphql | |
file: ./films.graphql |
docs/source/supergraphs.md
Outdated
people: | ||
routing_url: https://people.example.com | ||
schema: | ||
file: ./good-people.graphql |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
file: ./good-people.graphql | |
file: ./people.graphql |
@@ -8,21 +8,28 @@ module.exports = { | |||
options: { | |||
...themeOptions, | |||
root: __dirname, | |||
subtitle: 'Rover CLI', | |||
subtitle: 'Rover CLI (Preview)', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we drop the CLI
in the name or do you think that adds clarity @StephenBarlow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should keep "CLI" for the time being, until Rover has better name recognition via full release. Will be especially helpful in the docset switcher
the result of a command, whether that be SDL output, checks errors, or | ||
composition errors. | ||
```mermaid | ||
graph BT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
docs/source/supergraphs.md
Outdated
gateway --- serviceA & serviceB & serviceC; | ||
``` | ||
|
||
Rover commands that interact with subgraphs begin with `rover supergraph`. These commands primarily deal with composition of a **supergraph schema** that adheres to the [supergraph schema specification](https://apollo-specs.github.io/core/draft/pre-0). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rover commands that interact with subgraphs begin with `rover supergraph`. These commands primarily deal with composition of a **supergraph schema** that adheres to the [supergraph schema specification](https://apollo-specs.github.io/core/draft/pre-0). | |
Rover commands that interact with supergraphs begin with `rover supergraph`. These commands primarily deal with composition of a **supergraph schema** that adheres to the [supergraph schema specification](https://apollo-specs.github.io/core/draft/pre-0). |
Todo:
graph introspect
subgraph introspect
supergraph compose