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
ts second args dont working #956
Comments
indeed. The type inference from demo.mp4I can't tell if it's a limitation or a bug tho |
So it seems that the feature itself works as expected but the auto-complete is no longer useful, at least that's what I reproduced |
yeah I read the whole https://devblogs.microsoft.com/typescript/announcing-typescript-4-7 but I still don't understand why that didn't work anymore. Maybe it's related with Stricter Checks with Template String Expressions |
I found another type utility for the dot notation type inference here It does work but I didn't manage to make it work with |
Thanks for all your work on this @micalevisk Is there any chance of making
And still have |
@baconcheese113 it would introduce a breaking change. But yeah, we could change that in the next major release. I don't know why it is not the default behavior, tbh |
Oh additionally, we already validate the runtime value of our config object when registering the ConfigModule. So it would be nice if |
@baconcheese113 that's not feasible in TS, if I understood you correctly Please use our Discord server to discuss about it or other requests if you want to. |
Is there an existing issue for this?
Current behavior
Minimum reproduction code
https://github.com/productdevbook/nestjs_bug
Steps to reproduce
Expected behavior
jwt.private
etc typescript see. But dont seePackage version
2.1.0
NestJS version
8.4.6
Node.js version
v16.15.0
In which operating systems have you tested?
Other
No response
The text was updated successfully, but these errors were encountered: