Property with multiple type options destroys table layout
Not sure which part the parser picks its type declaration from, but I have a property defined with TypeScript as such:
/**
* (Description)
* @type string or Date
*/
datetime: {
type: [Date, String],
default: null,
} as PropOptions<Date | string | String>,
In Markdown the Type column is set to
`Date` | `String`
which leads to String
being put into the next column (Description). And since @type
seems to be ignored I can't even fix it manually.