-
-
Notifications
You must be signed in to change notification settings - Fork 723
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
Can't get MaxExecutionDepth option to work #1881
Comments
Can you oath the options into usedefaultpipeline? |
Moving the options inside UseDefaultPipeline() did not work. (See SO post) Or did you mean something else? Sorry if I misunderstand you. |
I see the problem I think ...
try this. |
@michaelstaib that took care of the execution depth, but my example was simplified; in reality, we also need some custom error filters like so:
How can I get the error filter registered as well? |
Error filters can be added through dependency injection. We are refining the api for 11 so that it becomes easier to configure. There are extension methods for error filters on service collection. |
That works--thank you for the quick response! |
Great, I am closing the issue. |
How do I get MaxExecutionDepth to work in Hot Chocolate GraphQL? Here is my code:
I've tested with this, even changing MaxExecutionDepth to 1, but I can still execute 20+ deep queries.
Also made an SO post. The answer suggesting I move the options inside UseDefaultPipeline() did not work.
Posted in the Slack yesterday but no response; figured I should post an issue instead.
HC version: 10.4.0
Edit: Also occurring in 10.4.3
The text was updated successfully, but these errors were encountered: