Experimental legacy decorators vs tsc@5+ decorators

[hardy613]

The typescript announcement of v5 included a new proposal for decorators that is a breaking change from the legacy experimental decorators. It is said the both decorator types can be supported, but migrating to v5 decorators includes well typed versions of the decorators. It can therefore become confusing within the type system of decorator functions when supporting both legacy and v5+ decorators.

More information from the typescript team announcement. Please see a more detailed article on the changes.

As noted in the article changes to

@ClassDecorator()
export class MyClass {}

Changes to

export
@ClassDecorator()
class MyClass {}

The community is against the export change and it has not been enforced. An open (good faith) discussion on this part of the proposal will be open in the future. While this change currently does not affect this project, it is an example of how even the adopted proposals are not completely ready for a wider support.

These changes to adopted early stage proposals and the possible affect that could have on this project, I recommend that we only support legacy experimental decorators until later stages of the decorator proposals.

[WillForrestMindBridge]

I haven't found any official big super-thread or discussion about the syntax about retaining both syntaxes and/or reverting it in later typescript versions. Just the good faith discussion comment.

i guess we need to give it a few more years?

[hardy613]

I haven't found any official big super-thread or discussion about the syntax about retaining both syntaxes and/or reverting it in later typescript versions. Just the good faith discussion comment.

i guess we need to give it a few more years?

same here, which makes it all a little confusing already. I hope it is less than a few years for sure, but until something hits a better proposal stage, waiting seems to be our best option.