Fix README grammar
This commit is contained in:
parent
be4c352939
commit
0531bf7790
1 changed files with 5 additions and 6 deletions
|
@ -14,11 +14,10 @@
|
|||
[#170](https://github.com/graphql-rust/juniper/pull/170)
|
||||
|
||||
- Large integers (> signed 32bit) are now deserialized as floats. Previously,
|
||||
they produced the "integer out of range" error. For languages that do not
|
||||
have distinction between integer and floating point types (including
|
||||
javascript), this means large floating point values which do not have
|
||||
fractional part could not be decoded (because they are represented without
|
||||
a decimal part `.0`).
|
||||
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`).
|
||||
|
||||
[#179](https://github.com/graphql-rust/juniper/pull/179)
|
||||
|
||||
|
@ -50,7 +49,7 @@
|
|||
|
||||
[#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)
|
||||
|
||||
|
|
Loading…
Reference in a new issue