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
[Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
When an enum is defined to be used later on multiple places using ref, the output Avro schema will put empty value on type property attribute of ref property. See samples below for better understanding.
openapi-generator version
lateset build from master and release: 5.3.1
OpenAPI declaration file content or url
openapi: 3.0.0info:
title: Money event schemadescription: | Specification for the the MoneyEvent and all subtypesversion: 0.1.0servers: []paths: {}components:
schemas:
MoneyEventType:
description: 'The kind of monetary transaction'type: stringenum:
- x1
- x2MoneyEvent:
description: 'A event describing some kind of monetary transaction'required:
- eventTypeproperties:
eventType:
$ref: '#/components/schemas/MoneyEventType'
Generation Details
generating models is enough to see invalid output for MoneyEvent:
{
"namespace": "models",
"type": "record",
"doc": "A event describing some kind of monetary transaction",
"name": "MoneyEvent",
"fields": [
{
"name": "eventType",
"type": ,
"doc": ""
}
]
}
Suggest a fix
The fix should be as simple as changing the mustache template for typeProperty in avro
The text was updated successfully, but these errors were encountered:
Bug Report Checklist
Description
When an enum is defined to be used later on multiple places using ref, the output Avro schema will put empty value on
type
property attribute of ref property. See samples below for better understanding.openapi-generator version
lateset build from master and release: 5.3.1
OpenAPI declaration file content or url
Generation Details
generating models is enough to see invalid output for MoneyEvent:
Suggest a fix
The fix should be as simple as changing the mustache template for typeProperty in avro
The text was updated successfully, but these errors were encountered: