You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is possible right now (or good practice). When I build the schema everything goes fine, but when I try and use GraphiQL to query
page { header { title}}
I get this
{ "statusCode": 400, "error": "Bad Request", "message": "User Error: expected iterable, but did not find one for field Page.header." }
Something like the following is what I tried instead of having every object into its own schema. I'm still relatively new to best practices of mongo, but thought it would make for faster queries. My thinking for this was my collections would be only users and pages. Instead of users, pages, headers, contents, footers... etc.
Not sure if this is possible right now (or good practice). When I build the schema everything goes fine, but when I try and use GraphiQL to query
page { header { title}}
I get this
{ "statusCode": 400, "error": "Bad Request", "message": "User Error: expected iterable, but did not find one for field Page.header." }
Something like the following is what I tried instead of having every object into its own schema. I'm still relatively new to best practices of mongo, but thought it would make for faster queries. My thinking for this was my collections would be only users and pages. Instead of users, pages, headers, contents, footers... etc.
The text was updated successfully, but these errors were encountered: