Error with nested classes order about typegoose

[szokodiakos]

Thank you for your report @JoseLuisGarciaOtt. Yes currently Job must be defined before User. I will investigate this further and update you about this.

[szokodiakos]

@JoseLuisGarciaOtt I investigated the issue, and came up with a solution: you could pass the Job class explicitly to the prop decorator as a subdoc property for example. I've implemented the feature quickly, then the following TypeScript error rose:

So it means that TypeScript won't actually let me use the class before declaration. The example provided in the documentation is wrong, i will update it, however the "workaround" must be used.

Or if you put each class to a separate file, then the import order should not matter (take a look at the tests for an example structure).

And I will try to add a more clear error message to prevent this happening in the future.

[szokodiakos]

I've created #9 as an enhancement task in which I add documentation and error message to make it more clear.

[JoseLuisGarciaOtt]

You are right. I thought classes definitions were hoisted, but only their bindings are... just like in the case of let and const: they indeed exist, but aren't yet initialized.

So yes, just change the doc and we are done :)

[szokodiakos]

Right! :) Closing this one.