arthurvaverko

Facing the same issue ... did anyone found a workaround bside defining the directive on every field of the resolver ?

Jumping in here .. some Apollo ref for namespacing [Apollo docs separation of concern with namespacing](https://www.apollographql.com/docs/technotes/TN0012-namespacing-by-separation-of-concern/) We also use namespaces .. Under root query we have some "me" queries related...

```javascript import _ from 'lodash' import {Microfiber as IntrospectionManipulator} from 'microfiber' const {get, sortBy} = _ export default ({ introspectionResponse, graphQLSchema: _graphQLSchema, allOptions: _allOptions, introspectionOptions, }) => { const introspectionManipulator...

This is exactly the issue I'm facing .. any due date on this merge ?

just hit the same issue using the following setup in cloudformation to reproduce .. ```yaml Resources: RawDLKDataStagingBucket: Type: AWS::S3::Bucket Properties: BucketName: raw-dlk-data-staging FRTAppPlatformBucket: Type: AWS::S3::Bucket Properties: BucketName: frt-app-platform AppEuropeTestEntityCRUDTopic: Type:...