Description

Title. Basically just makes it accept an undefined value for targetKey, which stops TypeScript from complaining about it.

Related Issue

1556

Motivation and Context

I want to upgrade Typescript to v5 and use @targetName().

See https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#more-accurate-type-checking-for-parameter-decorators-in-constructors-under-experimentaldecorators

How Has This Been Tested?

Not a functional change, but rather a type change. That said, npm teststill passes. Furthermore, TypeScript v5.x.x no longer shows errors when using @targetName().

Types of changes

[ ] Updated docs / Refactor code / Added a tests case (non-breaking change)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[ ] I have updated the changelog.

inversify / InversifyJS

Fix `@targetName()` signature on TypeScript 5 #1561