Open vsusaya opened 5 years ago
Reusing this issue for a related question - but how do I go about using additional properties? I'm noticing that when I have a RAML object
type with additionalProperties
set to true, it gets generated as its own class, but that class does not have a reference to a map or other structure that would allow for setting of fields that are not predefined. I have tried this with the config <includeAdditionalProperties>
set to true.
I have the following RAML, which defines a type where I want to restrict the type of any additional properties. This is valid RAML based on the 1.0 specification. It seems that the
//
field is treated as having an empty string value as a name which throws an index out of bounds exception during code generation (please also see the stack trace below).Any chance there's a known workaround?