From cb40e111a3467b5befd5a279eecbfbfe0584261b Mon Sep 17 00:00:00 2001 From: Vladimir Razuvaev Date: Fri, 22 Sep 2017 23:16:34 +0700 Subject: [PATCH] v0.11.1 --- CHANGELOG.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c47ee36..2b1bd16 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,20 +1,22 @@ # Changelog +#### v0.11.1 +- Ability to override internal types via `types` option of the schema (see #174). + ## 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) 2. It may break existing applications because scalar input coercion rules are stricter now:
-
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` -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). Improvements: - Stricter input coercion (see #171) -- 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) +- Types built with `BuildSchema` now have reference to AST node with corresponding AST definition (in $astNode property) +- Account for query offset for error locations (e.g. when query is stored in `.graphql` file) #### v0.10.2 - StandardServer improvement: do not raise an error when variables are passed as empty string (see #156)