@@ -16,20 +16,20 @@ The reference implementation provides base libraries in JavaScript that would
16
16
provide the basis for full GraphQL implementations and tools. It is not a fully
17
17
standalone GraphQL server that a client developer could use to start
18
18
manipulating and querying data. Most importantly it provides no mapping to a
19
- functioning, production-ready backend. The only “backend” we have targeted for
20
- this early preview are in-memory stubs in test cases.
19
+ functioning, production-ready backend. The only “backend” that we have targeted for
20
+ this early preview, are in-memory stubs in test cases.
21
21
22
- We are releasing this now because after GraphQL was first discussed publicly,
22
+ We are releasing this now, because after GraphQL was first discussed publicly,
23
23
many engineers used this information to implement the parts of the system that
24
24
we discussed publicly. We want to support those engineers by providing both a
25
25
formal specification and a reference implementation for the system as a whole.
26
26
27
- To that end the target audience is not the client developer, but those who have
28
- or are actively interested in building their own GraphQL implementations and
29
- tools. Critically we also want feedback on system and to incorporate that
27
+ To that end the target audience is not the client developer, but those who have,
28
+ or are actively interested in, building their own GraphQL implementations and
29
+ tools. Critically we also want feedback on the system and to incorporate that
30
30
feedback in our final release.
31
31
32
- In order to be broadly adopted GraphQL will have to target a wide
32
+ In order to be broadly adopted, GraphQL will have to target a wide
33
33
variety of backends, frameworks, and languages, which will necessitate a
34
34
collaborative effort across projects and organizations. This technical preview
35
35
marks the beginning of that process.
0 commit comments