Yeah, by the definition of cascade it doesn’t seem expected behavior. But now we are not asking cascade on fields but on fragments+fields and fragments are entirely graphql features.
So first, we need to support cascade on fragments, that will be added in graphql. And then this case will be handed. Currently we don’t have any plan for it but we will discuss it internally and then see if we need to prioritize it.