You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
delete d: '' from the return object of the abridgedObject function
run yarn test
see working test
Context (Environment)
Version of the library: 3.2.1
Version of NodeJS: 12.18.2
Confirm you were using yarn not npm: [x]
Detailed Description
Thanks to the intel of @fantapop (#749 (comment)) and microsoft/TypeScript#26238 (comment) I was able to determine the cause of the truncation to be a missing ts.NodeBuilderFlags.NoTruncation flag in some of the TS functions used by tsoa.
With this flag in place, the output of TS won't be truncated.
Breaking change?
This change might lead to a different output of tsoa, however this should not result in regressions and if so, due to errors which were silent otherwise.
The text was updated successfully, but these errors were encountered:
Sorting
I'm submitting a ...
I confirm that I
Expected Behavior
This should not break
tsoa swagger
ortsoa routes
.Current Behavior
See #749 and possibly #681
TSOA is not using
ts.NodeBuilderFlags.NoTruncation
which leads to issues like those mentioned or like the following:Possible Solution
See working patch: master...cellular:feature/patch_truncation_issue_781
I am working on creating/submitting a PR based on it.
Steps to Reproduce
yarn build
yarn test
d: ''
from the return object of theabridgedObject
functionyarn test
Context (Environment)
Version of the library: 3.2.1
Version of NodeJS: 12.18.2
Detailed Description
Thanks to the intel of @fantapop (#749 (comment)) and microsoft/TypeScript#26238 (comment) I was able to determine the cause of the truncation to be a missing
ts.NodeBuilderFlags.NoTruncation
flag in some of the TS functions used bytsoa
.With this flag in place, the output of TS won't be truncated.
Breaking change?
This change might lead to a different output of
tsoa
, however this should not result in regressions and if so, due to errors which were silent otherwise.The text was updated successfully, but these errors were encountered: