You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 4, 2017. It is now read-only.
Copy file name to clipboardExpand all lines: public/docs/ts/latest/cookbook/graphql.jade
-6Lines changed: 0 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -148,8 +148,6 @@ include ../_util-fns
148
148
will merge those into one single network request and GraphQL will send back the information in one single response, with exactly the information we need -
149
149
no more, no less and no need to do complex joins and waiting to responses on the client.
150
150
151
-
> Example
152
-
153
151
### Typed API and tooling
154
152
155
153
By now, we all understand the benefits of Typescript for our code.
@@ -158,10 +156,6 @@ include ../_util-fns
158
156
Why don’t we do the same for our API? Where sometimes is written by another team and we can’t really know what is going to change there?
159
157
160
158
With GraphQL, the schema is typed and shared between the client and the server so we can get the same benefits when working with the network - validation and autocompletion inside our IDE at development time!
0 commit comments