This commit is contained in:
Vladimir Razuvaev 2017-09-22 23:16:34 +07:00
parent f7248dec76
commit cb40e111a3

View File

@ -1,20 +1,22 @@
# Changelog # Changelog
#### v0.11.1
- Ability to override internal types via `types` option of the schema (see #174).
## v0.11.0 ## v0.11.0
This release brings little changes, but there are two reasons why it is released as major version: This release brings little changes but there are two reasons why it is released as major version:
1. To follow reference implementation versions (it matches 0.11.x series of graphql-js) 1. To follow reference implementation versions (it matches 0.11.x series of graphql-js)
2. It may break existing applications because scalar input coercion rules are stricter now:<br> 2. It may break existing applications because scalar input coercion rules are stricter now:<br>
<br>
In previous versions sloppy client input could leak through with unexpected results. In previous versions sloppy client input could leak through with unexpected results.
For example string `"false"` accidentally sent in variables was converted to boolean `true` For example string `"false"` accidentally sent in variables was converted to boolean `true`
and passed to field arguments. In new version such input will produce an error and passed to field arguments. In the new version, such input will produce an error
(which is a spec-compliant behavior). (which is a spec-compliant behavior).
Improvements: Improvements:
- Stricter input coercion (see #171) - Stricter input coercion (see #171)
- Types built with `BuildSchema` now have reference to ast node with corresponding AST definition (in $astNode property) - Types built with `BuildSchema` now have reference to AST node with corresponding AST definition (in $astNode property)
- Account for query offset for errors (e.g. when query is stored in `.graphql` file) - Account for query offset for error locations (e.g. when query is stored in `.graphql` file)
#### v0.10.2 #### v0.10.2
- StandardServer improvement: do not raise an error when variables are passed as empty string (see #156) - StandardServer improvement: do not raise an error when variables are passed as empty string (see #156)