-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Current spec does not say anything about representing Enums in the interchange json. Current plugin implementation outputs this for a enum into the json file:
"TransportEventType_Code": {
"name": "TransportEventType_Code",
"type": "Enum",
"isAbstract": false,
"description": "",
"Property": [],
"Enum": [
{
"name": "Call",
"description": "",
"tags": []
},
{
"name": "Arrival",
"description": "",
"tags": []
},
{
"name": "Departure",
"description": "",
"tags": []
},
{
"name": "Loading",
"description": "",
"tags": []
},
{
"name": "UnLoading",
"description": "",
"tags": []
},
{
"name": "BorderCrossing",
"description": "",
"tags": []
},
{
"name": "TransShipment",
"description": "",
"tags": []
},
{
"name": "Stop",
"description": "",
"tags": []
}
]
},Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels