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
Hello,
This is mainly a question/discussion that I wanted to start.
I am one of the maintainers of inversify which is a DI library . A very very common question we get is "when are we switching to vanilla decorators". Since inversify or mostly other DI libraries are all doing parameter decorations using the experimentalDecorators flag, supporting stage 3 decorators would be close to impossible with the same UX.
The question would be, has anything changed in the statements of tc39 or is this still something with low interest ?
The text was updated successfully, but these errors were encountered:
NestJS is also a library which heavily uses DI and parameter decorators, and this feature (along with decorator metadata), are needed to support vanilla decorators. It would enable us to use tooling such as esbuild with NestJS.
Hello,
This is mainly a question/discussion that I wanted to start.
I am one of the maintainers of
inversify
which is a DI library . A very very common question we get is "when are we switching to vanilla decorators". Sinceinversify
or mostly other DI libraries are all doing parameter decorations using theexperimentalDecorators
flag, supporting stage 3 decorators would be close to impossible with the same UX.The question would be, has anything changed in the statements of tc39 or is this still something with low interest ?
The text was updated successfully, but these errors were encountered: