Call the correct method of oneof examples

[MintsInc]

Context

PR #3177 fixed constructor collisions in oneOf types by using static factory methods when multiple types have the same type erasure (e.g., List<String> and List<Double> both erase to List). However, the example generation code was not updated to use these new factory methods, causing compilation failures in generated examples.

Issue

The failing example in PR #3057 attempted to instantiate CustomAttributeValuesUnion with a List<String>:

new CustomAttributeValuesUnion(Arrays.asList("Abba", "The Cure"))  // ❌ Constructor doesn't exist

This fails because CustomAttributeValuesUnion has:

• oneOf: String, List<String>, Double, List<Double>
• Regular constructors for String and Double (no collision)
• Static factory methods for List<String> and List<Double> (collision detected)

Changes

Updated .generator/src/generator/formatter.py to detect type erasure collisions when generating examples:

1. _format_oneof(): Now calls prepare_oneof_methods() to determine whether to use a regular constructor or static factory method
2. format_data_with_schema_list(): Same collision detection for list-based oneOf types

The example generator now correctly produces:

CustomAttributeValuesUnion.fromStringList(Arrays.asList("Abba", "The Cure"))  // ✓ Correct

Test

This fix resolves the compilation failure in PR #3057's UpdateCaseCustomAttribute.java example.

[MintsInc]

• Call the correct method of oneof examples #3180 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.