Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
When we have a oneOf containing two complex types with the same base type (
List<String>
andList<Double>
for example), it causes compilation errors in Java:List<String>
andList<Double>
erase toList
)getList()
for both types)This issue will surface in PR #3057 which introduces
CustomAttributeValuesUnion
with oneOf:String
,List<String>
,Double
,List<Double>
.Changes
Implemented collision detection and resolution for oneOf types with the same type erasure. The logic has been placed in the Python generator (rather than the Jinja2 template) for better separation of concerns and maintainability.
Added
prepare_oneof_methods()
function informatter.py
:Updated
modelOneOf.j2
template:prepare_oneof_methods()
functionMethod generation strategy:
String
,Double
): Generate regular constructors + simple getters (getString()
,getDouble()
)List<String>
,List<Double>
): Generate static factory methods + descriptive gettersfromStringList(List<String>)
,fromDoubleList(List<Double>)
getStringList()
,getDoubleList()
Test
I've tested that on the changes from the problematic PR and I got this result: