File tree Expand file tree Collapse file tree 1 file changed +7
-5
lines changed Expand file tree Collapse file tree 1 file changed +7
-5
lines changed Original file line number Diff line number Diff line change 11# Changelog
22
3+ #### v0.11.1
4+ - Ability to override internal types via ` types ` option of the schema (see #174 ).
5+
36## v0.11.0
4- This release brings little changes, but there are two reasons why it is released as major version:
7+ This release brings little changes but there are two reasons why it is released as major version:
58
691 . To follow reference implementation versions (it matches 0.11.x series of graphql-js)
7102 . It may break existing applications because scalar input coercion rules are stricter now:<br >
8- <br >
911In previous versions sloppy client input could leak through with unexpected results.
1012For example string ` "false" ` accidentally sent in variables was converted to boolean ` true `
11- and passed to field arguments. In new version such input will produce an error
13+ and passed to field arguments. In the new version, such input will produce an error
1214(which is a spec-compliant behavior).
1315
1416Improvements:
1517- Stricter input coercion (see #171 )
16- - Types built with ` BuildSchema ` now have reference to ast node with corresponding AST definition (in $astNode property)
17- - Account for query offset for errors (e.g. when query is stored in ` .graphql ` file)
18+ - Types built with ` BuildSchema ` now have reference to AST node with corresponding AST definition (in $astNode property)
19+ - Account for query offset for error locations (e.g. when query is stored in ` .graphql ` file)
1820
1921#### v0.10.2
2022- StandardServer improvement: do not raise an error when variables are passed as empty string (see #156 )
You can’t perform that action at this time.
0 commit comments