Commit 0b885b2e authored by Luke Duncalfe's avatar Luke Duncalfe

Remove max_complextiy and max_depth calls

These values are always set dynamically within `#multiplex` based on the
`current_user`. Previously `#multiplex` was overriding them. It's less
confusing to simply not call them at all, to avoid people needing to
understand how these calls affected the resulting `max_complextiy` and
`max_depth` (they didn't).
parent 4e14ce1f
......@@ -20,9 +20,6 @@ class GitlabSchema < GraphQL::Schema
query_analyzer Gitlab::Graphql::QueryAnalyzers::LoggerAnalyzer.new
query_analyzer Gitlab::Graphql::QueryAnalyzers::RecursionAnalyzer.new
max_complexity DEFAULT_MAX_COMPLEXITY
max_depth DEFAULT_MAX_DEPTH
query Types::QueryType
mutation Types::MutationType
subscription Types::SubscriptionType
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment