Will Dembinski
Will Dembinski
Same! Is that thing?
lol - i need this too!
Very broken, very sad :(
Why is this constantly a problem with this lib
@ortonomy - We have a pattern where on every request, we instantiate an object where all Repos are 'bound' to a manager (in a transaction) and all operations reference that...
Steelman-ing the decision - the pattern moves to a function invocation (vs. a class inheritance pattern) - it might just be more ergonomic and guide developers to use the library...
@IonVillarreal - We do this: ```ts import { AbstractRepository, CustomRepositoryCannotInheritRepositoryError, CustomRepositoryNotFoundError, Repository, getMetadataArgsStorage, } from "typeorm"; import type { EntityManager, ObjectType } from "typeorm"; export const createGetCustomRepository = (manager: EntityManager)...
Just out of curiosity - would something like simply removing: ``` this.props.params this.props.location this.props.history this.props.routes this.props.route this.props.routeParams ``` Be a solution? Ultimately tucking all those props into the `router` itself?...
This worked for typescript atm ```ts function requireUncached(modulePath: string): any { try { // Resolve the module path to get the absolute path const resolvedPath = require.resolve(modulePath); // Delete the...
Hey @tynes we spoke about landing these changes are separate PRs. But there were some consistency/non-determinism issues I thought we should chat about first!