-
Notifications
You must be signed in to change notification settings - Fork 41
Issues: slicknode/graphql-query-complexity
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Include meta fields (__typename, __type, __schema) against total field complexity [2]
#92
by Squarix
was merged May 28, 2024
Loading…
fix(ESM package): QueryComplexity import CJS module from GraphQL
#91
by hqtoan94
was merged Jun 10, 2024
Loading…
Include meta fields (__typename, __type, __schema) against total field complexity
#90
by jvanst
was closed May 28, 2024
Loading…
Default non-defined graphql operations to have 0 complexity
#89
by BasKiers
was merged May 28, 2024
Loading…
Add path of GraphQL node being evaluated to estimator args
#83
by eduhenke
was closed Dec 14, 2022
Loading…
import
graphql/**/*.mjs
instead of graphql/**/*.js
files in ESM build output
#80
by andresusanto
was closed Aug 29, 2022
Loading…
Add a context option for passing the request context to estimators
#77
by hayes
was merged Aug 27, 2022
Loading…
Error Cannot use GraphQLSchema "[object GraphQLSchema]" from another module or realm.
#75
by jer-sen
was closed Jun 10, 2024
Is there a way to assign complexities to mutations, objects and fields by default ?
#74
by bozvul993
was closed Jul 24, 2022
Feature Request: Complexity estimator receives all args to be used as multiplier factor
#71
by ale7canna
was closed Feb 2, 2022
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.