How to use entity repository in service without injecting

[Quadriphobs1]

How to use entity repository in service without injecting

[B4nan]

I still don't follow what you mean. So you don't like the InjectRepository bit, but are fine with using nest DI in general? You can make the repository injectable, the decorator is needed only when you do not have custom implementation.

This is how the repositories are registered, you can use the same way to register your custom repository:

https://github.com/mikro-orm/nestjs/blob/master/src/mikro-orm.providers.ts#L63

{
  provide: CustomAuthorRepository, 
  useFactory: (em: EntityManager) => em.getRepository(Author),
  inject: [EntityManager],
}

Or as long as you name your custom repository the same way as getRepositoryToken() helper would, you don't need to do anything special:

@Repository()
export class AuthorRepository ... {}

constructor(private repo: AuthorRepository) {}

[B4nan]

You define the custom repository, and it will be used automatically. If you use @Repository() decorator, you need to make sure the file will be loaded, so the decorator can be executed (without that, the ORM does not know about such repository).

One way to make sure the file will be loaded is to link it from the entity definition. To do so, you can use EntityRepositoryType, that will also allow inference of the type of the repository:

@Entity()
export class Author {

  [EntityRepositoryType]: CustomAuthorRepository;

}

Now this ensures the @Repository() decorator will be executed and custom repository will be registered. The em.getRepository(Author) will be correctly typed to CustomAuthorRepository.

constructor(
  @InjectRepository(Author)
  private readonly articleRepository: CustomAuthorRepository,
) {}

[Quadriphobs1]

Hmmm... Having to go through the @InjectResitory seems a little bit overly roundtrip to me, I was actually hoping for a way to either register it through the module as a provider or something just as services can be registered using the provider

[Quadriphobs1]

Ohhh that seems better... Having to put the decorator on the repository is what I was actually concerned about... but removing also do the trick...

[nikkonrom]

Is there any way to specify [EntityRepositoryType]: CustomAuthorRepository; while defining entities through EntitySchema? customRepository: () => CustomAuthorRepository, seems to not fixing the problem.

[B4nan]

Just put it to the class/interface:

export interface IAuthor4 {
  [EntityRepositoryType]: AuthorRepository;
  id: number;
  name: string;
  email: string;
}

export const Author4 = new EntitySchema<IAuthor4>({
  name: 'Author4',
  properties: {
    id: { type: 'number', primary: true },
    name: { type: 'string' },
    email: { type: 'string', unique: true },
  },
  customRepository: () => AuthorRepository,
});

You need both, EntityRepositoryType is for TS inference, customRepository is for the ORM runtime metadata.