search

raindigi / GraphqlType-API-Registration

Graphql Tutorial Example with typeORM for building a scalable Back-End API and caches management
MIT License
1 stars 1 forks source link

[Snyk] Upgrade graphql-query-complexity from 0.2.3 to 0.11.0 #156

Open snyk-bot opened 2 years ago

snyk-bot commented 2 years ago

Snyk has created this PR to upgrade graphql-query-complexity from 0.2.3 to 0.11.0.

merge advice :information_source: 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.11.0 - 2021-11-08

    Breaking

    • Drop support for GraphQL < v14.6

    New

    • Add support for GraphQL JS v16
    • ESM module support
  • 0.10.0 - 2021-10-28

    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
  • 0.9.0 - 2021-08-09

    New Features

    • Compiles code into ES Modules as well as common JS modules (#37)
    • Adds createComplexityRule named export to main package
  • 0.8.1 - 2021-05-04

    Fixes

    • Adds support for default values of query variables. Fixes #50

    Improvements

    • Add prettier code formatting
    • Simplify eslint rules
    • FIx linter setup
  • 0.8.0 - 2021-03-18

    New Features

    • The GraphQL node is now available inside of the estimator #46
  • 0.7.2 - 2020-11-20

    v0.7.2

  • 0.7.1 - 2020-11-01

    Fixes

    • Fix issue with fields with optional directive property #34
  • 0.7.0 - 2020-08-12

    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
  • 0.6.0 - 2020-05-25

    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

    • Improved TS types #28

    Thanks to @ rh389, @ wSedlacek

  • 0.5.0 - 2020-04-17

    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
  • 0.4.1 - 2019-10-21
  • 0.4.0 - 2019-10-06
  • 0.3.0 - 2019-05-18
  • 0.2.3 - 2019-02-14
from graphql-query-complexity GitHub release notes
Commit messages
Package name: graphql-query-complexity
  • d59c636 v0.11.0
  • db460a2 Add GraphQL v16 support #66 (#68)
  • c7ebf14 Fix tests for graphql v14.x, up min required version to GraphQL v14.6.0
  • 0d9c412 Fix hybrid test initialization
  • cb16cb5 Move createComplexityRule out of index file #65
  • a66211a Add hybrid module test setup for ESM, CommonJS tests #65
  • 79ed658 Fix hybrid module setup #65
  • d24b9fd v0.10.0
  • c8950d6 Link Slicknode in README
  • 91d1f86 Fix return values for invalid score
  • a2e4439 Update dev dependencies
  • d8396b3 Drop support for graphql < v14.5.0
  • 7d045b1 Add handling for invalid argument values, error reporting in getComplexity function #61
  • a940f94 v0.9.0
  • a54894f Add ES module support #37 (#56)
  • 33b1fbf v0.8.1
  • 0d340b2 Add support default values for query variables, fixes #50 (#52)
  • 8e19e3f Setup Prettier code style (#51)
  • 9db9914 Fix linter setup (#49)
  • a7a5042 v0.8.0
  • 581ab04 Update README
  • 3c37d91 Merge pull request #46 from noc7c9/master
  • 6e0e3ff Add node to ComplexityEstimatorArgs
  • d2fc8b3 Merge pull request #43 from dimatill/feature/export-complexity-directive
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

stale[bot] commented 2 years ago

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.