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

Add links to the book for 0.10.0 features

Browse source
This commit is contained in:
Christian Legnitto 2018-09-13 23:33:25 -07:00 committed by GitHub
parent 347777a8d0
commit 50a9fa31b6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
changelog/0.10.0.md
View file

@ -24,13 +24,13 @@
- The `GraphQLObject`, `GraphQLInputObject`, and `GraphQLEnum` custom derives - The `GraphQLObject`, `GraphQLInputObject`, and `GraphQLEnum` custom derives
now parse doc strings and use them as descriptions. This behavior can be now parse doc strings and use them as descriptions. This behavior can be
overridden by using an explicit GraphQL `description` annotation such as overridden by using an explicit GraphQL `description` annotation such as
`#[graphql(description = "my description")]`. `#[graphql(description = "my description")]`. [View documentation](https://graphql-rust.github.io/types/objects/defining_objects.html#defining-objects).
[#194](https://github.com/graphql-rust/juniper/issues/194) [#194](https://github.com/graphql-rust/juniper/issues/194)
- Introduced `IntoFieldError` trait to allow custom error handling - Introduced `IntoFieldError` trait to allow custom error handling
i.e. custom result type. The error type must implement this trait resolving i.e. custom result type. The error type must implement this trait resolving
the errors into `FieldError`. the errors into `FieldError`. [View documentation](https://graphql-rust.github.io/types/objects/error_handling.html#structured-errors).
[#40](https://github.com/graphql-rust/juniper/issues/40) [#40](https://github.com/graphql-rust/juniper/issues/40)
@ -40,7 +40,7 @@
- Error responses no longer have a _data_ field, instead, error details are stored in the _extensions_ field - Error responses no longer have a _data_ field, instead, error details are stored in the _extensions_ field
**Note:** while this is a breaking change, it is a necessary one to better align with the latest [GraphQL June 2018](https://facebook.github.io/graphql/June2018/#sec-Errors) specification, which defines the reserved _extensions_ field for error details. **Note:** while this is a breaking change, it is a necessary one to better align with the latest [GraphQL June 2018](https://facebook.github.io/graphql/June2018/#sec-Errors) specification, which defines the reserved _extensions_ field for error details. [View documentation](https://graphql-rust.github.io/types/objects/error_handling.html#structured-errors).
[#219](https://github.com/graphql-rust/juniper/pull/219) [#219](https://github.com/graphql-rust/juniper/pull/219)
@ -49,7 +49,7 @@
[#225](https://github.com/graphql-rust/juniper/issues/225) [#225](https://github.com/graphql-rust/juniper/issues/225)
* When using the `GraphQLObject` custom derive, fields can now be omitted by annotating the field with `#[graphql(skip)]`. * When using the `GraphQLObject` custom derive, fields can now be omitted by annotating the field with `#[graphql(skip)]`. [View documentation](https://graphql-rust.github.io/types/objects/defining_objects.html#skipping-fields).
[#220](https://github.com/graphql-rust/juniper/issues/220) [#220](https://github.com/graphql-rust/juniper/issues/220)