So you’ve run into the requirement yourself.
I was mainly suggesting a generic approach because the team is actively adding new functionality to the context object like the realtime livequery and subscriptions. Even third parties like zenstack used it to simplify code passthroughs and I can’t really imagine them shipping a setup with that kind of typescript ‘patch’ … and there may be others like them in the future.
zenstack source: New "How To" for implementing flexible authorization
Is there a reason why you didn’t choose a more generic approach here?
Is it just not possible?