add-entity

To add a new EF Core entity, define a sealed AggregateRoot<Guid> with a private EF constructor, static factory, behavior methods, and domain event raising, then apply framework-aligned EF Core configuration without manual tenant or soft-delete query filters.

Configuring multitenancy and soft delete for an Entity Framework Core aggregate requires using the kit's EF Core configuration conventions for table mapping and constraints, deliberately avoiding manual query filters for tenant or soft-delete behavior.

Yes, creating a domain-driven design aggregate root with EF Core requires a private EF constructor to ensure encapsulation, alongside a static factory for instantiation and behavior driven through methods rather than public property setters.

Creating a PostgreSQL migration for a new domain entity involves running the EF Core migration workflow using the specified PostgreSQL migrations project and the target DbContext to ensure the new aggregate is persisted correctly.

No, you should not use manual query filters for tenant and soft delete behaviors in EF Core configurations; the framework handles these automatically through its marker-interface-driven conventions and base entity configurations.

Domain events should be raised via the kit's DomainEvent helpers when adding an entity to maintain consistency with the framework's domain-driven design architecture and ensure production-grade event handling within the aggregate root.