Collections with Primary Key Field set to Auto-incremented integer or Auto-incremented big integer doesn't have the id property set to required as oppose to collections where the id type is set to Generated UUID.
This issue causes clients such as Orval to generate types with optional id.
"ItemsUUID": {
"type": "object",
"properties": {
"id": {
"nullable": false,
"type": "string",
"format": "uuid"
},
"name": {
"nullable": true,
"type": "string"
}
},
"x-collection": "uuid",
"required": [
"id"
]
},
"ItemsInteger": {
"type": "object",
"properties": {
"id": {
"nullable": false,
"type": "integer"
},
"name": {
"nullable": true,
"type": "string"
}
},
"x-collection": "integer"
}
}
Collections with
Primary KeyField set toAuto-incremented integerorAuto-incremented big integerdoesn't have the id property set to required as oppose to collections where the id type is set toGenerated UUID.This issue causes clients such as Orval to generate types with optional id.