Naming collision with DocumentType in generated mock code

[dafurman]

Bug report

This is similar to #2708 but it only concerns mocks, so it seemed worth treating as a separate issue.

I have a enum type DocumentType that conflicts with ApolloAPI.DocumentType in generated mock code.
Would it be possible to prefix generated types in mocks with the schemaName they're living in to resolve ambiguity?

Versions

Please fill in the versions you're currently using:

• apollo-ios SDK version: 1.0.5
• Xcode version: 14.1
• Swift version: 5.7
• Package manager: Swift Package Manager

Steps to reproduce

To reproduce this you will have to use a scheme that defines DocumentType as an enum type.

Further details

#2679 seemed to fix this issue for the main generated code, but I'm still experiencing this issue for generated mocks.
If I manually specify the type as coming from my generated package - GQLTypes, I can get the mocks compiling successfully:

public struct MockFields {
    @Field<GraphQLEnum<GQLTypes.DocumentType>>("documentType") public var documentType
}

[calvincestari]

Thanks for creating the issue @dafurman. @AnthonyMDev and I are working on resolving these type name conflicts once and for all. We'll get these resolved.

[calvincestari]

@dafurman, apologies for the delay in this issue but it is now fixed, merged and will go out in the next release.