-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] tst-reflect: You call getType() method directly. You have probably wrong configuration, because tst-reflect-transformer package should replace this call by the Type instance. #75
Comments
Hi @Manik-Jain, The problem is that So in that case it will not use the tst-reflect-transformer. So I looked up this issue nestjs/nest-cli#1208.
is quite... pointless... since So I was looking for some options to disable that building by
So you have to use Or second option is to use ts-patch, which will override |
@Manik-Jain Closing for now, it helped I suppose. Let me know if it doesn't. |
Related #37 |
Hi @Hookyns thanks for suggesting the work around, it worked for me. |
Your tests? What kind of issues? BTW Jest is configured in this repo and it works just fine. |
I'm running the tests with
tsconfig.json
And getting the following error for each line of code that uses tst-reflect
|
Your Jest configuration use TS files from |
I had a similar issue. I run my tests from the
|
Describe the bug
I have been using this library with NestJS and Typescript, with essentially the same configurations mentioned in readme, to instantiate my objects at runtime.
Observation:
The code executes like 1/5 runs, and fails otherwise with the error :
tst-reflect: You call getType() method directly. You have probably wrong configuration, because tst-reflect-transformer package should replace this call by the Type instance.
The code causing the problem
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Code shall execute successfully each time without any issues
Runtime (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: