We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hot Chocolate
14
N/A
We're using the AddGraphQLFunction() extension method in our project which in turn calls
AddGraphQLFunction()
graphql-platform/src/HotChocolate/AspNetCore/src/AspNetCore/Extensions/HotChocolateAspNetCoreServiceCollectionExtensions.cs
Line 103 in ad8fdf0
Some way to override the cost analyzer and disable it would be nice since we don't have any use for the cost directives.
The option to disable cost analyzer exists
No option to disable the cost analyzer exists
No response
The text was updated successfully, but these errors were encountered:
Does this not have the desired effect?
services .AddGraphQLServer(...) .ModifyCostOptions(options => options.EnforceCostLimits = false)
Sorry, something went wrong.
Does this not have the desired effect? services .AddGraphQLServer(...) .ModifyCostOptions(options => options.EnforceCostLimits = false)
The schema still has @cost on all the mutations and queries even with this code.
@cost
No branches or pull requests
Product
Hot Chocolate
Version
14
Link to minimal reproduction
N/A
Steps to reproduce
We're using the
AddGraphQLFunction()
extension method in our project which in turn callsgraphql-platform/src/HotChocolate/AspNetCore/src/AspNetCore/Extensions/HotChocolateAspNetCoreServiceCollectionExtensions.cs
Line 103 in ad8fdf0
AddGraphQLFunction()
extension method.Some way to override the cost analyzer and disable it would be nice since we don't have any use for the cost directives.
What is expected?
The option to disable cost analyzer exists
What is actually happening?
No option to disable the cost analyzer exists
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: