Closed hpx7 closed 7 months ago
This was a bug in the old implementation, but we should support this.
@WoH I'm happy to try and contribute support for this, would you be able to provide any guidance for how this should be done?
This should result in:
{
"type": "object",
"properties": {
},
"additionalProperties": false
}
Right?
This is what it generates on 5.1.1:
"Record_string.never_": {
"properties": {},
"type": "object",
"description": "Construct a type with a set of properties K of type T"
},
Since we are now trying to descend into the indexed type in a Mapped Type, we need to probably try to check if the indexType is the never type and handle that separately: https://github.com/lukeautry/tsoa/blob/master/packages/cli/src/metadataGeneration/typeResolver.ts#L242
Thanks for the tip, I created https://github.com/lukeautry/tsoa/pull/1537
Resolved in v6.0.1
Sorting
I'm submitting a ...
I confirm that I
Expected Behavior
In 5.1.1, tsoa was able to handle the following type (which represents an empty object, i.e.
{}
)Current Behavior
This breaks starting in 6.0.0-rc.0
Possible Solution
Steps to Reproduce
Context (Environment)
Version of the library: 6.0.0 Version of NodeJS: 18.17.1
Detailed Description
Breaking change?
This is a breaking change in tsoa version 6