Contributions
Allow yaml to define enum with different name and value
A common practice is to use enum to define coded persistence values such as: Status: type: string enum: - name: ABANDONED value: A - name: ISSUED value: I However this generates a JSON object as the value ABANDONED_A("{name: ABANDONED, value: A}") Is this not possible with OAS3?15KViews0likes3Comments