Simplify DbContext by extracting aggregate configuration into dedicated classes

[tjementum]

Summary & Motivation

Remove the need for centralized configuration in the DbContext when defining aggregates in a self-contained system. Previously, the DbContext required a DbSet<T> property for each aggregate (table) and explicit configuration in OnModelCreating for strongly typed IDs and other EF configurations like .HasOne<T>(), .WithMany(), .OnDelete(), .ToJson(), etc. Over time, this made the DbContext in a self-contained system big and hard to maintain

With this change, all entity configurations are moved to dedicated classes implementing IEntityTypeConfiguration<T>, keeping each aggregate's configuration within its vertical slice. The SharedKernelDbContext now automatically discovers and registers these configurations, eliminating the need for central configuration.

Additionally, the DbContext now uses a convention-based approach to create tables, leveraging Humanizer for pluralizing table names. This removes the need to define DbSet<T> properties explicitly, making the DbContext a lightweight class used only in repositories without requiring customization for new aggregates.

Downstream Projects

Extract an AggregateConfiguration file for each aggregate, where the content should match the current configuration in OnModelCreating in the self-contained system’s DbContext. Example:

namespace PlatformPlatform.AccountManagement.Features.Signups.Domain;

public sealed class SignupConfiguration : IEntityTypeConfiguration<Signup>
{
    public void Configure(EntityTypeBuilder<Signup> builder)
    {
        builder.MapStronglyTypedUuid<Signup, SignupId>(a => a.Id);
        builder.MapStronglyTypedNullableId<Signup, TenantId, string>(u => u.TenantId);
    }
}

All properties for tables should be removed from DbContext. Any direct usage of these should be replaced by DbSet in the repository. Example:

// Before:
return accountManagementDbContext.Signups.Where(s => ...);

// After:
return DbSet.Where(s => ...);

Checklist

• I have added tests, or done manual regression tests
• I have updated the documentation, if necessary

[linear]

PP-309 Use IEntityTypeConfiguration to isolate Entity Framework configuration of aggregates

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
96.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud