Skip to content
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

chore: clarify drawbacks of introspection publish #866

Merged
merged 1 commit into from
Oct 7, 2021

Conversation

EverlastingBugstopper
Copy link
Contributor

publishing via introspection is a bit more lossy than publishing SDL directly

@@ -89,6 +89,8 @@ If your schema isn't stored in a compatible file, you can provide `-` as the val
rover graph introspect http://localhost:4000 | rover graph publish my-graph@dev --schema -
```

We recommend publishing a `.graphql` file directly over publishing from introspection because introspection will strip comments and most directive usages.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Whenever possible, we recommend publishing a .graphql file directly instead of using introspection. An introspection result omits schema comments and most uses of directives."

Copy link
Contributor

@StephenBarlow StephenBarlow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with small language suggestion!

@EverlastingBugstopper EverlastingBugstopper force-pushed the avery/clarify-introspection-publish branch from 9c49b07 to 5771920 Compare October 7, 2021 20:52
@EverlastingBugstopper EverlastingBugstopper merged commit e7c9cf2 into main Oct 7, 2021
@EverlastingBugstopper EverlastingBugstopper deleted the avery/clarify-introspection-publish branch October 7, 2021 22:54
@EverlastingBugstopper EverlastingBugstopper added this to the 0.4.0 milestone Oct 19, 2021
This was referenced Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants