yume/juniper
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update quickstart.md

Browse source
This commit is contained in:
Christian Legnitto 2020-07-15 21:24:57 -10:00 committed by GitHub
parent 5ddd2d499f
commit c4319b6449
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/book/content/quickstart.md
View file

@ -22,7 +22,7 @@ naturally map to GraphQL features, such as `Option<T>`, `Vec<T>`, `Box<T>`,
For more advanced mappings, Juniper provides multiple macros to map your Rust
types to a GraphQL schema. The most important one is the
[object][jp_object] procedural macro that is used for declaring an object with
[graphql_object][graphql_object] procedural macro that is used for declaring an object with
resolvers, which you will use for the `Query` and `Mutation` roots.
```rust
@ -132,7 +132,7 @@ We now have a very simple but functional schema for a GraphQL server!
To actually serve the schema, see the guides for our various [server integrations](./servers/index.md).
You can also invoke the executor directly to get a result for a query:
Juniper is a library that can be used in many contexts--it does not require a server and it does not have a dependency on a particular transport or serialization format. You can invoke the executor directly to get a result for a query:
## Executor
@ -202,4 +202,4 @@ fn main() {
[rocket]: servers/rocket.md
[iron]: servers/iron.md
[tutorial]: ./tutorial.html
[jp_obj_macro]: https://docs.rs/juniper/latest/juniper/macro.object.html
[graphql_object]: https://docs.rs/juniper/latest/juniper/macro.graphql_object.html