Switching from a TypeOrm custom repository to Injectable NestJs providers can be a smooth transition with the

Question

Switching from a TypeOrm custom repository to Injectable NestJs providers can be a smooth transition with the

After updating TypeORM to version 0.3.12 and @nestjs/typeorm to version 9.0.1, I followed the recommended approach outlined here.

I adjusted all my custom repositories accordingly, but simply moving dependencies into the providers metadata of the createTestingModule doesn't seem to be sufficient.

The line

dailyTaskRepository = module.get<TypeOrmDailyTaskRepository>(TypeOrmDailyTaskRepository)

may be outdated, leaving me unsure how to retrieve the provider from the module.

Below is the full code:

daily-task.typeorm.inte.ts

(insert modified code here)

The console error message reads:

(insert console error message here)

typescript nestjs repository typeorm

Answer 1

Answer №1

I came across the solution thanks to this discussion: https://stackoverflow.com/a/74729950/11698451

It was necessary for me to utilize TypeOrmModule.forFeatue() and provide it with all the entities. Thus, my code looked like this:

  beforeAll(async () => {
    const module = await Test.createTestingModule({
      imports: [
        TypeOrmModule.forRoot(config.db),
        TypeOrmModule.forFeature([
          Task,
          Student,
          Metrics,
          Task,
          Activity,
          Template,
          Plan,
          Workout,
          Meeting,
          Record,
          Performance,
        ]),
      ],
      providers: [
        AthleteRepository,
        BiometricsRepository,
        DailyTaskRepository,
        ExerciseRepository,
        TemplateRepository,
        ProgramRepository,
        WorkoutRepository,
        SessionRepository,
        PerformanceRepository,
      ],
    }).compile()

    dailyActivityRepository = module.get<DailyTaskRepository>(
      DailyTaskRepository,
    )

    await dailyTaskRepository.query('SET FOREIGN_KEY_CHECKS=0')
    await dailyTaskRepository.query(`DELETE FROM daily_task;`)
    await generateTasksFixtures(dailyTaskRepository)
  })

Answer 2

I came across the solution thanks to this discussion: https://stackoverflow.com/a/74729950/11698451

It was necessary for me to utilize TypeOrmModule.forFeatue() and provide it with all the entities. Thus, my code looked like this:

  beforeAll(async () => {
    const module = await Test.createTestingModule({
      imports: [
        TypeOrmModule.forRoot(config.db),
        TypeOrmModule.forFeature([
          Task,
          Student,
          Metrics,
          Task,
          Activity,
          Template,
          Plan,
          Workout,
          Meeting,
          Record,
          Performance,
        ]),
      ],
      providers: [
        AthleteRepository,
        BiometricsRepository,
        DailyTaskRepository,
        ExerciseRepository,
        TemplateRepository,
        ProgramRepository,
        WorkoutRepository,
        SessionRepository,
        PerformanceRepository,
      ],
    }).compile()

    dailyActivityRepository = module.get<DailyTaskRepository>(
      DailyTaskRepository,
    )

    await dailyTaskRepository.query('SET FOREIGN_KEY_CHECKS=0')
    await dailyTaskRepository.query(`DELETE FROM daily_task;`)
    await generateTasksFixtures(dailyTaskRepository)
  })

Switching from a TypeOrm custom repository to Injectable NestJs providers can be a smooth transition with the

Answer №1

Similar questions

What is the best way to manage a promise in Jest?

utilize makeStyles to modify button text color

What are the steps for implementing the ReactElement type?

Updating from React 17 to React 18 in Typescript? The Children of ReactNode type no longer supports inline conditional rendering of `void`

Improprove the types generated from GraphQL responses

Angular - Loading images on the fly

Using Typescript to configure a custom proxy in a Create React App

Angular Error: Trying to access a property on an undefined variable

Enrolling a new plugin into a software repository

Introducing the concept of type-specific name inclusion

When defining a class property in TypeScript, you can make it optional by not providing

The 'type' property is not present in the 'ChartComponent' type, however, it is necessary in the 'ApexChart' type

Designing a versatile Angular component for inputting data (Mailing Address)

Typescript: The original type cannot be indexed with a type-mapped type

The data type 'string | number | boolean' cannot be assigned to type 'undefined'. Specifically, the type 'string' is incompatible with type 'undefined'. Error code: ts(2322)

Error encountered when attempting to assign a value of the original data type within the Array.reduce function

React Type Mutation response feedback is a valuable tool for receiving input

``Changing the value of a class variable in Angular 2 does not result in the

Implementing generics in TypeScript for objects made easy with this guide!

The solution to automatically delete orphaned rows in TypeORM