We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
The issue: microsoft/TypeScript#52435
In TS 5.0, you will get that error when using any @inject since we should allow undefined for constructor parameter decorating.
@inject
undefined
Expected behavior
tsyringe/src/decorators/inject.ts
Line 11 in f738999
The type of propertyKey should be propertyKey: string | symbol | undefined. NestJS has already made their fix here: nestjs/nest#10970
propertyKey
propertyKey: string | symbol | undefined
Version: ^4.5.0
The text was updated successfully, but these errors were encountered:
I've also found the issue with the Params Decorator Type in tsyringe, while Inversify hasn't encountered any issues yet.
Even though "experimentalDecorators": true has been enabled, there are still issues with backward compatibility for Decorators Type.
Sorry, something went wrong.
I've also found the issue with the Params Decorator Type in tsyringe, while Inversify hasn't encountered any issues yet. Even though "experimentalDecorators": true has been enabled, there are still issues with backward compatibility for Decorators Type.
Same problem for me !
Xapphire13
Successfully merging a pull request may close this issue.
Describe the bug
The issue: microsoft/TypeScript#52435
In TS 5.0, you will get that error when using any
@inject
since we should allowundefined
for constructor parameter decorating.Expected behavior
tsyringe/src/decorators/inject.ts
Line 11 in f738999
The type of
propertyKey
should bepropertyKey: string | symbol | undefined
. NestJS has already made their fix here: nestjs/nest#10970Version:
^4.5.0
The text was updated successfully, but these errors were encountered: