Skip to content

Propose updates to GraphQL extensibility doc #404

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Propose updates to GraphQL extensibility doc #404

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4085808
Propose updates to GraphQL extensibility doc
DrewML Jul 17, 2020
346bd5c
Update design-documents/graph-ql/extensibility.md
DrewML Jul 21, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update design-documents/graph-ql/extensibility.md 
Co-authored-by: Alex Paliarush <[email protected]>
  • Loading branch information
@DrewML @paliarush
DrewML and paliarush authored Jul 21, 2020
commit 346bd5cdab23bca88062327b473c3f8aaa495f77
2 changes: 1 addition & 1 deletion design-documents/graph-ql/extensibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ It should be possible to make the following changes to a schema, _without_ intro
- Add optional arguments to a query/mutation (some backwards-compat risks)
- Add extra data to the output of a mutation (backwards-compatible)

The following patterns should be followed to ensure our schema remains extensible, with _minimal_ (ideally no) breaking changes._
The following patterns should be followed to ensure our schema remains extensible, with _minimal_ (ideally no) breaking changes.

## Backwards-Compatible GraphQL Schema Development Patterns

Expand Down