How to avoid circular references brought by decorator?

[shrinktofit]

This may be a long long discussion..

[shrinktofit]

Intro

Why type and type decorators are needed?

Creator(especially starting from Cocos Creator 3D) usually expects to understand the type information(let's say, type) of a class field. Editor uses that type to determine what a value is allowed to feed for the property and how it should properly show that field.

Sometimes Editor may deduce directly from the fields' runtime value, once if:

• its type is definitely one of the primitive type or a class type.

In all other cases Editor is unable to deduce, for example:

• it's of enumeration type: value of enumeration type is just a primitive type, but its acceptable values are limited;
• it's of array type: JavaScript arrays are un-typed; Editor is unable to deduce the element type;
• it's of null-able or, in general, variant types: such as Node | null, TypeA | TypeB.

As a result, Creator provides a serial of (legacy) decorators to allow developers to manually specify the type information.

Decorators are executed in module execution stage. Let's skip the stuffs that how ES modules are imported. Only thing you should know is: since sometimes these decorators need types exported from another modules, the circular reference problem is a real headache.

[shrinktofit]

Progress

Recently I found that block decorator proposal may help to this! See tc39/proposal-decorators#340 for my post.