Autogenerated TestMocks files don't have access to SchemaGraphQL "schemaNamespace" in main target

[Karram-Ayman]

Question

Hey Team,
using:
apollo-ios-cli --version
1.23.0

I’ve integrated ApolloTestSupport into our project, which uses Apollo via an XCFramework, and I’ve configured mock generation in the Apollo Codegen config as follows:

"output": {
      "testMocks": {
        "absolute": {
          "path": "./MyAppTests/ApolloGraphQL/ApolloGenerated/TestMocks",
          "targetName": "MyAppTests"
        }
      },
      "operations": {
        "inSchemaModule": {}
      },
      "schemaTypes": {
        "path": "./MyApp/ApolloGraphQL/ApolloGenerated/",
        "moduleType": {
          "embeddedInTarget": {
            "name": "MyApp"
          }
        }
      }
    }

The mock files are generated correctly under the MyAppTests target. However, I’m encountering the following error in the generated mock files:

// @generated
// This file was automatically generated and should not be edited.

import ApolloTestSupport
import MyApp

public class Campaign: MockObject {
  public static let objectType: ApolloAPI.Object = SchemaGraphQL.Objects.Campaign
  public static let _mockFields = MockFields()
  public typealias MockValueCollectionType = Array<Mock<Campaign>>
}

❗️Cannot find 'SchemaGraphQL' in scope — this module is generated in the MyApp target.

Question

Is there a supported way to make Apollo Codegen use:

@testable import MyApp instead of  import MyApp 

n the generated mock files? That would allow access to internal symbols without needing to make everything public.

Any advice or alternative approaches would be appreciated!

[BobaFetters]

@Karram-Ayman The use case you described isn't currently supported without making things public as you said. Although I think we should probably just make the schema module always be a @testable import for the test mocks by default. I will add this to our backlog and look to implement that soon for an upcoming release.

[Karram-Ayman]

Thanks @BobaFetters this would be great if you will implement this in upcoming release as making things public for our internal SDKs could make naming conflicts with integration in main repo + seems that "accessModifier": "public" doesn't work for a reason on our internal SDK

[github-actions]

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better.