I expect pagination to work in conjunction with cascade but that does not seem to be true (at least in GraphQL).
I have a query that returns around 15K nodes and want to get the first 5 that match the @cascade directive as well. The result is 0. However if I remove the pagination limit then I get all the ones that match cascade.
I believe the problem is that pagination happens before the cascade directive on the rood of the query. Is there a way to reverse this order? I don’t see any need why someone would want to paginate and then apply a cascade directive 
This will return all of the completed Tasks:
query {
queryTask @cascade {
name
completed
}
}
This should return the first 5 completed Tasks, but it instead returns an empty set:
query {
queryTask(first: 5) @cascade {
name
completed
}
}
I understand for performance that pagination reduces the load much faster then cascade does, but I do not believe that is the understood effect. This will probably be a pain to fix and cause performance issues 