Type: Array and nullable: true does not render nullable
Open
Nobody has claimed this yet.
help wanted
Type: Bug
- Dominant language
- TypeScript
- Stars
- 25.9k
- Forks
- 2.4k
- Avg merge
- 13h 10m
- Merged PRs (30d)
- 4
Description
I have a response which either returns an array or null. I specify the return json schema with:
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "array",
"uniqueItems": true,
"items": {
....
}
"nullable": true
}
But redoc does not render this like for other types e.g. integers.
I currently use the following workaround:
{
"$schema": "http://json-schema.org/draft-07/schema#",
"oneOf": [
{
"type": "array",
"uniqueItems": true,
"items": {
"$ref": "../shared/id.json#"
}
},
{
"type": "any"
"nullable":true
}
]
}

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported OpenAPI schema in Redoc and compare nullable array rendering with nullable integer rendering. Trace the schema-rendering entry point for array types; done means an array with nullable: true is visibly rendered as allowing null, without requiring the oneOf workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100