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

Fix README grammar

Browse source
This commit is contained in:
Christian Legnitto 2018-09-13 11:10:02 -07:00 committed by GitHub
parent be4c352939
commit 0531bf7790
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
changelog/0.10.0.md
View file

@ -14,11 +14,10 @@
[#170](https://github.com/graphql-rust/juniper/pull/170) [#170](https://github.com/graphql-rust/juniper/pull/170)
- Large integers (> signed 32bit) are now deserialized as floats. Previously, - Large integers (> signed 32bit) are now deserialized as floats. Previously,
they produced the "integer out of range" error. For languages that do not they produced an "integer out of range" error. For languages that do not
have distinction between integer and floating point types (including have a distinction between integer and floating point types (such as
javascript), this means large floating point values which do not have javascript), this meant large whole floating point values could not be
fractional part could not be decoded (because they are represented without decoded (because they were represented without a fractional value such as `.0`).
a decimal part `.0`).
[#179](https://github.com/graphql-rust/juniper/pull/179) [#179](https://github.com/graphql-rust/juniper/pull/179)
@ -50,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 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)]`.
[#220](https://github.com/graphql-rust/juniper/issues/220) [#220](https://github.com/graphql-rust/juniper/issues/220)