[Snyk] Upgrade graphql-query-complexity from 0.2.3 to 0.11.0 #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade graphql-query-complexity from 0.2.3 to 0.11.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: graphql-query-complexity
Breaking
New
Breaking:
getComplexity
now throws an error if the query complexity cannot be determined (invalid query, misconfiguration, etc.)Fixes:
New Features
createComplexityRule
named export to main packageFixes
Improvements
New Features
v0.7.2
Fixes
New Features
Breaking
legacyEstimator
and thefieldConfigEstimator
were removed in favor of thefieldExtensionsEstimator
. Adding support for GraphQL v15 made this necessary (see #30).estimator
option is now required when configuring the validation rule.New Features
Fixes
Thanks to @ rh389, @ wSedlacek
New Features
@ skip
and@ include
directives #23Commit messages
Package name: graphql-query-complexity
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs