CRD generation fails when walking the type hierarchy for enums #2819
Comments
metacosm
added a commit
that referenced
this issue
Feb 19, 2021
`Types.applyTypeArguments` doesn't crash when encountering differing cardinality between type definition and actual arguments, which was the case when encountering an enum property. Such properties are now generated by enumerating their cases name and recording them in the validation schema. Not sure if that actually covers all cases. Fixes #2819.
11 tasks
This was referenced Feb 20, 2021
Closed
metacosm
added a commit
that referenced
this issue
Feb 23, 2021
`Types.applyTypeArguments` doesn't crash when encountering differing cardinality between type definition and actual arguments, which was the case when encountering an enum property. Such properties are now generated by enumerating their cases name and recording them in the validation schema. Not sure if that actually covers all cases. Fixes #2819.
manusa
pushed a commit
that referenced
this issue
Feb 24, 2021
`Types.applyTypeArguments` doesn't crash when encountering differing cardinality between type definition and actual arguments, which was the case when encountering an enum property. Such properties are now generated by enumerating their cases name and recording them in the validation schema. Not sure if that actually covers all cases. Fixes #2819.
This was referenced Mar 12, 2021
This was referenced Mar 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The issue is that java describes enums as generic types of
java.lang.Enumwhich causes a mismatch between the number of arguments and the type definition inTypes.applyTypeArguments, causing anIndexOutOfBoundsException.The text was updated successfully, but these errors were encountered: