Issue: ABP Modular Angular application (Module Entity Referencing in Main DbContext (Potential Anti-Pattern))

[ayshamougamadou]

Hi,

I have a question regarding the usage of DbContext in both the host and modular applications within ABP.

In ABP modular applications, entities defined within a module are referenced in the module’s DbContext. However, it appears that the same entities also need to be referenced in the main application’s DbContext.

This approach seems to introduce tight coupling between the module and the main application. Ideally, a module should remain self-contained without requiring its entities to be referenced in the main application's DbContext.

Could you clarify why this is necessary? If this approach is intentional, are there best practices to mitigate the coupling while maintaining modularity?

this is the link to the article : https://abp.io/docs/latest/tutorials/modular-crm/part-03

Additionally, here are the respective DbContext implementations:

Module's DbContext:

Main Application's DbContext:

[realLiangshiwei]

You don't need to add it to your main application's DbContext.

The benefit of doing this is that it allows for some join queries.

See https://abp.io/docs/latest/framework/data/entity-framework-core/migrations#entityframeworkcore-project.