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

59 lines
2.7 KiB
Markdown
Raw Normal View History

0.10.0 release (#236) * Bump` juniper`, `juniper_codegen`, and `juniper_tests` versions. * Bump integration crate requirements to include 0.10.0. `juniper_iron` gets a semver breaking version as it has a breaking change but `juniper_iron` does not. * Move `juniper_rocket` changelog into one file. This aligns with `juniper_iron` and will be easier to automate in the future. * Let `juniper_warp` and `juniper_hyper` use `0.9.x` versions of Juniper. They don't rely on anything in 0.10.0 so don't require it.
2018-09-13 11:13:31 -05:00
# [0.10.0] 2018-09-13
## Changes
- Changed serialization of `NaiveDate` when using the optional `chronos` support.
**Note:** while this is not a Rust breaking change, if you relied on the serialization format (perhaps by storing serialized data in a database or making asumptions in your client code written in another language) it could be a breaking change for your application.
[#151](https://github.com/graphql-rust/juniper/pull/151)
- The `GraphQLObject`, `GraphQLInputObject`, and `GraphQLEnum` custom derives will reject
invalid [names](http://facebook.github.io/graphql/October2016/#Name) at compile time.
[#170](https://github.com/graphql-rust/juniper/pull/170)
- Large integers (> signed 32bit) are now deserialized as floats. Previously,
Fix README grammar
2018-09-13 13:10:02 -05:00
they produced an "integer out of range" error. For languages that do not
have a distinction between integer and floating point types (such as
javascript), this meant large whole floating point values could not be
decoded (because they were represented without a fractional value such as `.0`).
0.10.0 release (#236) * Bump` juniper`, `juniper_codegen`, and `juniper_tests` versions. * Bump integration crate requirements to include 0.10.0. `juniper_iron` gets a semver breaking version as it has a breaking change but `juniper_iron` does not. * Move `juniper_rocket` changelog into one file. This aligns with `juniper_iron` and will be easier to automate in the future. * Let `juniper_warp` and `juniper_hyper` use `0.9.x` versions of Juniper. They don't rely on anything in 0.10.0 so don't require it.
2018-09-13 11:13:31 -05:00
[#179](https://github.com/graphql-rust/juniper/pull/179)
- The `GraphQLObject`, `GraphQLInputObject`, and `GraphQLEnum` custom derives
now parse doc strings and use them as descriptions. This behavior can be
overridden by using an explicit GraphQL `description` annotation such as
`#[graphql(description = "my description")]`.
[#194](https://github.com/graphql-rust/juniper/issues/194)
- Introduced `IntoFieldError` trait to allow custom error handling
i.e. custom result type. The error type must implement this trait resolving
the errors into `FieldError`.
[#40](https://github.com/graphql-rust/juniper/issues/40)
- `GraphQLType` and `ToInputValue` are now implemented for Arc<T>
[#212](https://github.com/graphql-rust/juniper/pull/212)
- 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.
[#219](https://github.com/graphql-rust/juniper/pull/219)
* The `GraphQLObject` and `GraphQLInputObject` custom derives
now support lifetime annotations.
[#225](https://github.com/graphql-rust/juniper/issues/225)
Fix README grammar
2018-09-13 13:10:02 -05:00
* When using the `GraphQLObject` custom derive, fields can now be omitted by annotating the field with `#[graphql(skip)]`.
0.10.0 release (#236) * Bump` juniper`, `juniper_codegen`, and `juniper_tests` versions. * Bump integration crate requirements to include 0.10.0. `juniper_iron` gets a semver breaking version as it has a breaking change but `juniper_iron` does not. * Move `juniper_rocket` changelog into one file. This aligns with `juniper_iron` and will be easier to automate in the future. * Let `juniper_warp` and `juniper_hyper` use `0.9.x` versions of Juniper. They don't rely on anything in 0.10.0 so don't require it.
2018-09-13 11:13:31 -05:00
[#220](https://github.com/graphql-rust/juniper/issues/220)
* Due to newer dependencies, the oldest Rust version supported is now 1.22.0
[#231](https://github.com/graphql-rust/juniper/pull/231)
Reference in a new issue Copy permalink