Skip to content
This repository was archived by the owner on Dec 4, 2017. It is now read-only.

Commit 1358e69

Browse files
committed
docs(cookbook/graphql): Remove old comments
1 parent 453c0ae commit 1358e69

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

public/docs/ts/latest/cookbook/graphql.jade

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -148,8 +148,6 @@ include ../_util-fns
148148
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 -
149149
no more, no less and no need to do complex joins and waiting to responses on the client.
150150

151-
> Example
152-
153151
### Typed API and tooling
154152

155153
By now, we all understand the benefits of Typescript for our code.
@@ -158,10 +156,6 @@ include ../_util-fns
158156
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?
159157

160158
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!
161-
162-
163-
IDE GIF
164-
165159

166160
.l-main-section
167161
<a id="how-to"></a>

0 commit comments

Comments
 (0)