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
Hi @magicspon. With the provided clients from the package the idea is that nesting should not be a limiting factor for resolving a page. We fetch all the pages query time and then client-side or server-side construct the page tree itself to resolve a page by a path.
I think such an option could be possible to support, but I think it should not be necessary. Would you mind sharing a bit more on your setup? Maybe something can be changed there to fix this in another way.
It would be good to be able to prevent authors from nesting to far.
It'll also mean i can have a fixed depth in my groq query and be confident that I've got all the required slugs.
The text was updated successfully, but these errors were encountered: