Option to generate all / matching enum types regardless of whether they are used in operations

[hongping-quora]

Question

Apollo Koltin has an option alwaysGenerateTypesMatching:
https://www.apollographql.com/docs/kotlin/kdoc/older/3.8.2/apollo-gradle-plugin-external/com.apollographql.apollo3.gradle.api/-service/always-generate-types-matching.html

We were able to generate code with Apollo Kotlin for the enum types in the schema even if they aren't used by any queries or fragments by using .* with this option.

For Apollo iOS, we tried setting these options explicitly to false, but still didn't see the Swift code generated for the unused enum types from the schema.

• pruneGeneratedFiles
• reduceGeneratedSchemaTypes

The documentation in https://www.apollographql.com/docs/ios/code-generation/codegen-configuration
for reduceGeneratedSchemaTypes says

Defaults to false which generates Object types for all objects that implement any Interface referenced in operation documents.

While https://www.apollographql.com/docs/ios/docc/documentation/apollocodegenlib/apollocodegenconfiguration/outputoptions/reducegeneratedschematypes says

Whether to reduce the number of schema types that are generated to only those that are referenced in an operation.

Wondering if reduceGeneratedSchemaTypes should apply to enums that aren't referenced in an operation? If not, is there another option to do so?

Thanks!

[BobaFetters]

So by default the way code generation works is only types that are referenced in one of your operations have their code generated. The reduceGeneratedSchemaTypes is specifically meant to help further reduce the amount of generated code, because by default if an interface is used in an operation, then all object types which implement that interface get generated even if they arent explicitly used. So this option allows you to not generate those types and further reduce generated code size.

Currently there is no way to say "always generate these types" or specifically always generate all enum types. Although it is something the team can discuss.

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

[BobaFetters]

@hongping-quora Can I ask what your use case is for this? Would help give us a better understanding of the issue being solved with a feature like this.

[hongping-quora]

Thanks for the response!

We have a system where the GraphQL schema is generated from Python type and method definitions. The current behavior of our system is that the Python enums are only added to the schema if referenced by some GraphQL definition (e.g. a resolver or mutation). We are thinking of adding all enums to the schema regardless of whether they are referenced, so that they can be used in the iOS code, for other purposes as well such as logging using a non-GraphQL service.

However, just adding to the schema isn't sufficient on iOS, because the types also need to be used in some operation for corresponding Swift code to be generated.