Hello Prismic team
I'm working on a slice machine + GraphQL API solution for our blog redesign at getcircuit.com and I've hit the " 413 Request Entity Too Large" limitation while creating our new, content relationship-heavy, blog homepage.
I saw that I can try and minify the GraphQL to avoid this error up to some point but this solution is far from optimal and, considering our number of slices, that would at best earn us some time before becoming a problem again.
That said, are there any updates regarding the solutions suggested by @renaud on the 413 Request Entity Too Large thread?
At the moment, the internal discussion that we are having that we will have to either accept some predefined fragments to fetch allSlices (this is a solution that we have discussed in the past with @esmith) or to switch our API to accept POST request.