@@ -79,16 +79,16 @@ pub fn derive_scalar_value_internal(input: TokenStream) -> TokenStream {
7979The `impl_object` proc macro is the primary way of defining GraphQL resolvers
8080that can not be implemented with the GraphQLObject derive.
8181
82- It enables you to write GraphQL field resolvers for a type by declaring a
82+ It enables you to write GraphQL field resolvers for a type by declaring a
8383regular Rust `impl` block. Under the hood, the procedural macro implements
8484the GraphQLType trait.
8585
86- `impl_object` comes with many features that allow customization of
86+ `impl_object` comes with many features that allow customization of
8787your fields, all of which are detailed below.
8888
8989### Getting Started
9090
91- This simple example will show you the most basic use of `impl_object`.
91+ This simple example will show you the most basic use of `impl_object`.
9292More advanced use cases are introduced step by step.
9393
9494```
@@ -105,17 +105,17 @@ impl Query {
105105
106106
107107 // This defines a simple, static field which does not require any context.
108- // You can return any value that implements the `GraphQLType` trait.
108+ // You can return any value that implements the `GraphQLType` trait.
109109 // This trait is implemented for:
110110 // - basic scalar types like bool, &str, String, i32, f64
111111 // - GraphQL compatible wrappers like Option<_>, Vec<_>.
112112 // - types which use the `#derive[juniper::GraphQLObject]`
113113 // - `impl_object` structs.
114- //
115- // An important note regarding naming:
114+ //
115+ // An important note regarding naming:
116116 // By default, field names will be converted to camel case.
117117 // For your GraphQL queries, the field will be available as `apiVersion`.
118- //
118+ //
119119 // You can also manually customize the field name if required. (See below)
120120 fn api_version() -> &'static str {
121121 "0.1"
@@ -169,7 +169,7 @@ You can specify a context that will be available across
169169all your resolvers during query execution.
170170
171171The Context can be injected into your resolvers by just
172- specifying an argument with the same type as the context
172+ specifying an argument with the same type as the context
173173(but as a reference).
174174
175175```
@@ -198,11 +198,11 @@ impl Query {
198198 context.db.user(id)
199199 }
200200
201- // You can also gain access to the executor, which
201+ // You can also gain access to the executor, which
202202 // allows you to do look aheads.
203203 fn with_executor(executor: &Executor) -> bool {
204204 let info = executor.look_ahead();
205- // ...
205+ // ...
206206 true
207207 }
208208}
0 commit comments