Releases: slicknode/graphql-query-complexity
Releases · slicknode/graphql-query-complexity
v0.12.0
New
- Adds support for passing the execution context to estimators #77 (thanks @hayes)
Fixes
- Report variable coercion errors #78 (fixes #69)
v0.11.0
Breaking
- Drop support for GraphQL < v14.6
New
- Add support for GraphQL JS v16
- ESM module support
v0.10.0
Breaking:
- Support for GraphQL version < v14.5 was dropped
getComplexity
now throws an error if the query complexity cannot be determined (invalid query, misconfiguration, etc.)
Fixes:
- Invalid argument values in a query now have proper error handling (fixes #61 ) Thanks @dburles
v0.9.0
New Features
- Compiles code into ES Modules as well as common JS modules (#37)
- Adds
createComplexityRule
named export to main package
v0.8.1
Fixes
- Adds support for default values of query variables. Fixes #50
Improvements
- Add prettier code formatting
- Simplify eslint rules
- FIx linter setup
v0.8.0
New Features
- The GraphQL node is now available inside of the estimator #46
v0.7.1
Fixes
- Fix issue with fields with optional directive property #34
v0.7.0
New Features
- Handle complexity of abstract types (Union, Interface) by returning the maximum possible complexity for a field instead of the sum of the entire selection set, fixes #26
v0.6.0
Breaking
- The previously deprecated
legacyEstimator
and the fieldConfigEstimator
were removed in favor of the fieldExtensionsEstimator
. Adding support for GraphQL v15 made this necessary (see #30).
- The
estimator
option is now required when configuring the validation rule.
New Features
- Support for graphql-js v15 #30
Fixes
Thanks to @rh389, @wSedlacek
v0.5.0
New Features
- Add support for multi-query documents and calculating the complexity for a single operation #22
- Add support for
@skip
and @include
directives #23