Nine sounds generous on the face of it, but with all of the wrapping and grouping Prismic enforces it's actually not possible to query a scalar field on the fourth level of nesting, if the root is an
I'm trying to build a directory page showing all of the lessons available on an educational site. I have category -< course -< module -< unit. We have fewer than 100 units in total so displaying them all isn't unreasonable in one page and one query, but in graphql following Prismic's recommendation, a unit title's graphql path is:
allCategorys -> edges -> node -> courses -> course -> modules -> module -> units -> unit -> title
That's a query depth of 10, so the query fails. I'm still going to build this page, but I'm now going to have to split the query depth-wise and make more calls, which is inefficient for me and more costly for Prismic.
Would it be possible to reconsider this depth limit? Is a four level hierarchy really too much?