Why should we call the module twice?

I have one module in my app, with the last update I should write this:

@Module({
  imports: [
    TypeOrmModule.forRoot({
      /* Connection options goes here */,
      entities: [/* Entities goes here */],
    }),
    TypeOrmModule.forFeature([/* Entities goes here */]),
  ]
})

Why? I’ve already pass my entities inside options. And now I importing the same module twice.

[FriOne]

@obedm503 yeah, I have the same thought about it. It will be great if forRoot method creates repositories for entities if they was provided as classes array. We can have both methods implemented. Also forFeature name doesn’t explain what the function actually do. It is better to call it provideRepositories or smth like that.

[fwoelffel]

What about people who:

• uses forRoot in a DatabaseModule which exports the instanciated connection
• uses forFeature([ User ]) in a UserModule which imports the DatabaseModule
• uses forFeature([ Car ]) in a CarModule which imports the DatabaseModule
• doesn’t want the Repository<User> available in the CarModule
• doesn’t want the Repository<Car> available in the UserModule

I don’t think that what you’re asking for would allow that design.