A way to support transactions started without this library about typeorm-transactional-cls-hooked HOT 2 CLOSED

Thank you @Faithfinder...
The way the library works is that it starts a transaction and put the EntityManager within the cls-hook Namespace.
I don't see a real way of doing it the way you want, without changing the code of the callers...
I am sorry...

from typeorm-transactional-cls-hooked.

No worries. What I wanted to enable, is refactoring the code from the end of the call chain, rather than beginning. I suppose this library could somehow patch TypeORM's methods that start transactions to put the entity manager where we want it. The use case is not really worth the additional complexity though, probably.
The workaround is quite simple, if a bit ugly, really. I'll leave it here in case someone googles and stumbles upon this issue.

You can refactor the top level of transactional chain to use @Transactional() instead of getConnection().transaction(), and pass the manager further down the chain by getting the manager property of any repo you use. After that you can use both "styles" of transactions and refactor both the top and the bottom of the call chain at your leisure.

Pseudo code example. This:

  await getConnection().transaction(async transactionalEntityManager => {
     this.startTransactionalWork(transactionalEntityManager)
  });

startTransactionalWork(transactionalEntityManager) {
    const transactionalRepo = transactionalEntityManager.getRepository();
    continueTransactionalWork(transactionalEntityManager)
  }

becomes this:

@Transactional()
startTransactionalWork() {
    const transactionalEntityManager = this.anyInjectedRepository.manager;
    continueTransactionalWork(transactionalEntityManager)
  }

from typeorm-transactional-cls-hooked.