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
ok, actually I found another decorator @named can be used in normally, but still in documentation it indicates to use @targetName, is that a wrong description?
The error comes from the signature of @targetName not properly matching the decorator signature anymore.
It's new on Typescript 5: microsoft/TypeScript#52435
That said, I don't understand the difference between @named and @targetName. @named seems slightly better supported, and @targetName's docs mention the use of namedConstraint, which doesn't work because it works on a different tag.
Hey all, sorry for the delay. I'm starting to give some love the project again. This issue should be fixed in #1586. I'll release a new version soon :)
Expected Behavior
There should not be any error occurred when
@targetName
be used at constructorCurrent Behavior
constructor(@inject("IService") @targetName("queueService") ticketQueue: IService) { }
error TS1239: Unable to resolve signature of parameter decorator when called as an expression
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
Stack trace
The text was updated successfully, but these errors were encountered: