Shane Krueger

Results 854 comments of Shane Krueger

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

FYI, the computed complexity factor was 73706 and depth of 59.

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

(right or wrong)

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

The complexity code seems real stupid. It's got code like "if zero impact then use default" right after it's got ??= default. So you can't set a field to a...

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

@zspasojevic How do you think it should work? What do you want it to do?

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

The complexity is indeed calculated completely differently than it was in the past (see #2863), and I do not find it to be useful at this time. I suggest copying...

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

Note: the complexity of an introspection query is known to be approximately 73706 currently, even if it's stupid. See https://github.com/graphql-dotnet/graphql-dotnet/pull/3485/files

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

> I suggest copying the complexity analyzer from an earlier version and using it in your codebase. I can assist with that endeavor. Correction: this won't work because the complexity...

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

Complexity analyzer rewrite for v8: - #3989

Query is too complex to execute. The field with the highest complexity is: GraphQLParser.AST.GraphQLFragmentSpreadWithLocation

> With the changes to GraphQL Parser v7/v8 there is much more depth required than previously - around double most likely. > > I think we need to consider the...

upgradation of api from 3.1 to 6.0

Can you post the exact nuget GraphQL packages and version numbers you were using before and what ones you are trying to use now?