You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
When using a RAML that has for instance a response envelope:
myEnvelope that has some members in it, when creating a subtype, eg: EnvelopeForParticularResource it will generate enums and other types again, creating a change in the Java signature and therefore not compiling for the subtype.
When using a RAML that has for instance a response envelope:
myEnvelope
that has some members in it, when creating a subtype, eg: EnvelopeForParticularResource it will generate enums and other types again, creating a change in the Java signature and therefore not compiling for the subtype.See the following example project to reproduce raml-defined-example.tar.gz
As a dirty workaround I've been able to change the
type: mylib.myType
for antype: !include ...
which does the trick but is a far cry from ideal.The text was updated successfully, but these errors were encountered: