Vasil Rangelov

After some investigation into TypeORM's support, it seems they must first provide a way to configure a closure table (see typeorm/typeorm#5288) and also, adjacency lists are not supported in the...

Isn't the same true for a naming strategy though? If the key difference is type safety, maybe switch the template engine to this one: https://www.npmjs.com/package/typesafe-templates Either way, doing generation with...

But I'm talking about additional "child" templates... "partials" (see https://handlebarsjs.com/api-reference/runtime.html#handlebars-registerpartial-name-partial ), that add additional data in the output, not ones replacing the existing template. In such a setup, a fix...

Exactly. typeorm-model-generator may have empty files to appease handlerbars, but would not itself use those partials for any "actual" output. Any changes would be made into the template, not the...

I think a sufficient list of partials inside the main template would be - beforeImports - beforeEntityDecorators - beforeEntity - startOfEntity - beforeColumnDecorators - beforeColumn - afterColumn - beforeRelationDecorators -...

Huh... I didn't know there was a 3rd category. I thought there's only "lazy" and "eager". Well, no wonder I guess, given they're both the same type. The [related doc...

> It allows to visually assess if generated output is similar to desired one. This won't be possible with using pure sql queries. The "reference" folder is supposed to contain...

> You can achieve same thing right now using npm t -- --grep testName In the clone of the repo I have, running ```npm t -- --grep simple1-simple-entity``` or even...

I get that it might be more complex, so... A flag to toggle the old behaviour on inatall would be the next best thing. > but one thing that strikes...

@B4nan I have a potentially controversial proposal to solve this issue... Remove the ability to await the query builder. That is, instead of then(), name that method anything else.... like...