There's lots of redundancy in the API spec which leads to generation of duplicate but distinct / incompatible model classes during code generation. The "attachment" object type is only on of several places where this occurs in the spec, but I'd get feedback if this unification is desired first before investing more time in cleaning up definitions.pull/10178/head
parent
192367d6e3
commit
741ad6bf14
@ -0,0 +1,15 @@ |
||||
# Schema: Attachments |
||||
--- |
||||
type: object |
||||
properties: |
||||
_embedded: |
||||
type: object |
||||
properties: |
||||
elements: |
||||
type: array |
||||
readOnly: true |
||||
items: |
||||
allOf: |
||||
- "$ref": "./attachment_model.yml" |
||||
- description: Collection of Attachments |
||||
readOnly: true |
Loading…
Reference in new issue