Can we combine all of these queries? We have a lot of optimizations for multiple filters together.

I am guessing you have made the change from the RFC(requirement for @search), so that you don't have to use @cascade?

Why is the filter appearing here? I don't think it's required? I am guessing that your intention is that If someone has a filter on root query, we should propagate that here as well? The problem is, what if I want to do a nested query where y.s has some value, but i want to see all the order values for that y as well. Lets just make it a filter at the root level for now, and then we can add a new api for y { s }. Something like y @filter(s: eq()) {s}

This query seems unnecessary? We are just repeating the queryNested_X

Can you write one test around auth also? Where we have a auth filter on the query, so that we can make sure no uids are returned that shouldn't be

Is this required here? This makes it such that generated schema would contain this. From what I understand, you only need this in the tests?