Closed jhueppauff closed 1 year ago
Can you attach the schema?
You can also send us the schema in a private message on slack.chillicream.com
I need to clarify this. I know this makes it harder to diagnose. But it is an internal API and I am not sure if I am actually allowed to do this.
Does your schema has a type with more than 2 list levels ... like [[[Foo]]]
?
The validation check that throws detected a level of type depth greater than six which indicates that there must be a list structure deeper than three. Is this the case? We have limited list nesting to two levels as the spec only defines things to that level. It is not forbidden to have deeper nesting but what is the use-case for this and how deep is the nesting.
Yes, it seems so. I tried to remove those and it seems that those issues are gone now. I will check if I need those types at all . Will do more tests on Monday Thank you so far :)
How many levels of list does your schema have? We could increase it if there is a use-case for it that makes sense.
Is there an existing issue for this?
Product
Strawberry Shake
Describe the bug
We are trying to initialize a new project and fetching the schema from an external graphql endpoint.
dotnet graphql init https://some-graphql.endpoint/graphql
-n MyProject -p . -x "Authorization=Bearer xyz" -x "OtherHeader=value"Unfortunately it seems to fail as well if we try just to download the Schema.
We tried other Tools like Apollo to fetch the GraphQL Schema which works, but when we try to import from this file we get an error while building. But that might be due to different Schemas between Apollo and Strawberry?
Any Idea how to solve this?
Steps to reproduce
Relevant log output
No response
Additional Context?
No response
Version
13.0.5