Metadata file and the Type::findType(): Type | undefined and Type::getTypes(): Array<Type> methods

Suggestion

Add optional behavior or change the default behavior which will generate metadata.js file which will contain all the information about types at one place.

1. This should resolve the problem with circle dependencies,
2. no duplicit type declarations in generated .js files,
3. metadata can be used to find types eg. by name.

Example

const controllerType: Type = getType<Controller>();
const controllers = Type.getTypes().filter(type => type.isAssignableTo(controllerType));

---

Maybe something like @reflect() would be required to use on type declarations to optimize code. Or some configurations explicitly enabling metadata generation of all the types.

@reflect
export default class HomeController {}

[iDevelopThings]

I’m so confused… it’s now working fine for me O.o

[iDevelopThings]

Okay I think my main problem is just related to ts-node and the logic for this include/exclude system I’m working on.

I think it’s just a case of it not visiting the files defined, since i tapped some hacky logic onto the mainVisitor…

For this idea to work, it might have to be a program transformer O.o (this would probably be better any way for the fact we’re generating files… when i did a similar thing with webpack(just manual file creation) it sent it into an endless re-compile loop, which i haven’t considered)