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
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
Our API exchanges data between several systems. One of the differences between these systems is that one of them uses lowerstring-uuids and the other one uses upperstring-uuids. So we want to declare these IDs as "Uppercase" or "Lowercase" via typescript in there classes.
When using the Swagger-Plugin there recognized as "{}" and the Swagger-Plugin for TS-Jest throws with A circular dependency has been detected (property key: "id"). Please, make sure that each side of a bidirectional relationships are using lazy resolvers ("type: () => ClassType").
Describe the solution you'd like
It would be great if the Swagger plugin would treat "Uppercase" and "Lowercase" as normal strings.
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
Our API exchanges data between several systems. One of the differences between these systems is that one of them uses lowerstring-uuids and the other one uses upperstring-uuids. So we want to declare these IDs as "Uppercase" or "Lowercase" via typescript in there classes.
When using the Swagger-Plugin there recognized as "{}" and the Swagger-Plugin for TS-Jest throws with
A circular dependency has been detected (property key: "id"). Please, make sure that each side of a bidirectional relationships are using lazy resolvers ("type: () => ClassType").
Describe the solution you'd like
It would be great if the Swagger plugin would treat "Uppercase" and "Lowercase" as normal strings.
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
Reduce boilerplate.
Currently:
With wished feature:
The text was updated successfully, but these errors were encountered: