Swift 6's Upcoming Feature `InternalImportsByDefault` breaks generated schema/operations

[3redrubies]

Question

When building generated GraphQL targets in Swift 6 with InternalImportsByDefault enabled, the generated code imports cause ApolloAPI symbols to be treated as internal.

// Package.swift
.target(
    name: "GraphQLOperations",
    dependencies: [
        .product(name: "ApolloAPI", package: "apollo-ios"),
        "GraphQLSchema"
    ],
    swiftSettings: [
        .enableUpcomingFeature("InternalImportsByDefault") <-- This
    ]
),
.target(
    name: "GraphQLSchema",
    dependencies: [
        .product(name: "ApolloAPI", package: "apollo-ios")
    ],
    swiftSettings: [
        .enableUpcomingFeature("InternalImportsByDefault") <-- This
    ]
)

This forces downstream properties/types to be internal and results in compilation failures like:
Property must be declared internal because its type 'Object' uses an internal type

Is the team planning to support Swift’s InternalImportsByDefault feature (either now or closer to when it (maybe) becomes the default in Swift 7)?

Just wondering if this is on the radar yet or if it’s considered too early to address.

[3redrubies]

https://forums.swift.org/t/internal-imports-by-default-is-very-problematic-for-generated-code/82722

[BobaFetters]

@3redrubies This isn't something we plan to work on in the short term, more than likely we wouldn't look at this until closer to the release of Swift 7 if this is indeed going to be the default there. I added a ticket to make sure this is tracked here #3606

[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.