Skip to content

Commit a525a78

Browse files
author
James Baxley
authored
fix syntax for query type in breaking change example
1 parent 4de761c commit a525a78

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/source/guides/versioning.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ Since this is an _additive_ change, and doesn't actually change the default beha
101101
An example of a breaking change on an argument would be renaming (or deleting) an argument.
102102

103103
```graphql
104-
type query = {
104+
type Query {
105105
# What we have.
106106
getUsers(ids: [ID!], groupId: ID!): [User]!
107107

@@ -118,4 +118,4 @@ Instead of supporting it, if we wanted to remove the old argument, the safest op
118118

119119
Using an API management tool, like [Apollo Engine](https://www.apollographql.com/engine), its possible to determine when usage of an old field has dropped to an acceptable level and remove it and the earlier [field rollover](#field-rollover) section gives more info on how to do that.
120120

121-
Of course, it’s also possible to leave the field in place indefinitely!
121+
Of course, it’s also possible to leave the field in place indefinitely!

0 commit comments

Comments
 (0)