[Snyk] Upgrade graphql-query-complexity from 0.2.3 to 0.9.0 #133
+14
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade graphql-query-complexity from 0.2.3 to 0.9.0. See this package in npm: https://www.npmjs.com/package/graphql-query-complexity See this project in Snyk: https://app.snyk.io/org/saurabharch/project/01b33ceb-8fff-4724-9771-9cdb26440ad7?utm_source=github&utm_medium=upgrade-pr
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.9.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
-
0.9.0 - 2021-08-09
- Compiles code into ES Modules as well as common JS modules (#37)
- Adds
-
0.8.1 - 2021-05-04
- Adds support for default values of query variables. Fixes #50
- Add prettier code formatting
- Simplify eslint rules
- FIx linter setup
-
0.8.0 - 2021-03-18
- The GraphQL node is now available inside of the estimator #46
-
0.7.2 - 2020-11-20
-
0.7.1 - 2020-11-01
- Fix issue with fields with optional directive property #34
-
0.7.0 - 2020-08-12
- 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
-
0.6.0 - 2020-05-25
- The previously deprecated
- The
- Support for graphql-js v15 #30
- Improved TS types #28
-
0.5.0 - 2020-04-17
- Add support for multi-query documents and calculating the complexity for a single operation #22
- Add support for
-
0.4.1 - 2019-10-21
- Skip complexity calculation by directiveEstimator when astNode is undefined #21
-
0.4.0 - 2019-10-06
- Added field extensions estimator #19
-
0.3.0 - 2019-05-18
-
0.2.3 - 2019-02-14
from graphql-query-complexity GitHub release notesNew Features
createComplexityRulenamed export to main packageFixes
Improvements
New Features
v0.7.2
Fixes
New Features
Breaking
legacyEstimatorand thefieldConfigEstimatorwere removed in favor of thefieldExtensionsEstimator. Adding support for GraphQL v15 made this necessary (see #30).estimatoroption is now required when configuring the validation rule.New Features
Fixes
Thanks to @ rh389, @ wSedlacek
New Features
@ skipand@ includedirectives #23Bigfix release:
fieldConfigEstimatoris now deprecated in favor offieldExtensionsEstimatorCommit 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