In Schema ApplicantRelationshipType of OpenAPI descriptor submission-api-data.yaml the enum list is incorrectly listed with comma on MARRIED and REGISTERED_PARTNERSHIP, causing incorrect enum generation in Java class
ApplicantRelationshipType:
type: object
required:
- key
properties:
key:
$ref: '#/components/schemas/ApplicantRelationshipTypeKey'
ApplicantRelationshipTypeKey:
type: string
description: |
DE: Beziehungsart (nicht abschließende Aufzählung) z.B. (MARRIED=mit Ehepartner/in, REGISTERED_PARTNERSHIP=eingetragenem Lebenspartner/in, PARTNERSHIP=Lebenspartner/in). <br/>
EN: Open ended enum contains values for relation type, possible values are (MARRIED, REGISTERED_PARTNERSHIP, PARTNERSHIP)
x-extensible-enum:
- MARRIED,
- REGISTERED_PARTNERSHIP,
- PARTNERSHIP
- OTHER
The values should be listed without comma:
ApplicantRelationshipType:
type: object
required:
- key
properties:
key:
$ref: '#/components/schemas/ApplicantRelationshipTypeKey'
ApplicantRelationshipTypeKey:
type: string
description: |
DE: Beziehungsart (nicht abschließende Aufzählung) z.B. (MARRIED=mit Ehepartner/in, REGISTERED_PARTNERSHIP=eingetragenem Lebenspartner/in, PARTNERSHIP=Lebenspartner/in). <br/>
EN: Open ended enum contains values for relation type, possible values are (MARRIED, REGISTERED_PARTNERSHIP, PARTNERSHIP)
x-extensible-enum:
- MARRIED
- REGISTERED_PARTNERSHIP
- PARTNERSHIP
- OTHER
In Schema ApplicantRelationshipType of OpenAPI descriptor submission-api-data.yaml the enum list is incorrectly listed with comma on MARRIED and REGISTERED_PARTNERSHIP, causing incorrect enum generation in Java class
The values should be listed without comma: