esofar/dddify
50.8
Weak · 8 November 2026
4.5k
lines of production code
C#
primary language
7
measurements over time
What this system is
This system is a .NET library that enhances Entity Framework Core's DbContext configuration and soft-delete handling. It provides utilities for resolving service provider during registration, preserving owned entities during soft deletes, and improving API result wrappers and exception logging.
Behavioural changes
Enhanced DbContext configuration and soft-delete handling
The library now supports configuring DbContext options with access to the service provider, allowing resolution of configuration or hosting environment services during registration. For soft-deletable entities, the system now preserves owned entries during soft delete operations, ensuring related data is not inadvertently removed. Additionally, the API result wrapper now omits the 'data' field when it is the default value rather than just null, and exception logging now includes metadata from the API exception mapping.
src/Dddify · medium confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 47 → 51 (+4.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 76 → 76 (+0.0)
- Architecture 96 → 96 (-0.1)
- Maturity 39 → 66 (+27.0)
- Readiness 38 → 38 (+0.0)
- Security 73 → 64 (-9.4)
- Event-Driven 100 → 100 (+0.0)
- Performance 54 → 52 (-2.4)
Resolved (12)
- Duplicate intent: IUnitOfWork and UnitOfWork<TDbContext> expose identical persistence methods. IUnitOfWork is a generic interface that delegates to a specific DbContext, but UnitOfWork<TDbContext> exposes the exact same public API surface (SaveChangesAsync, Transaction management). This creates confusion about whether to depend on the generic interface or the concrete generic class, and duplicates the contract.
- Inconsistent configuration entry points: Localization can be added via the main DddifyOptionsBuilder.AddLocalization (with or without config section path) OR via a dedicated extension JsonLocalizationOptionsExtension. This splits the configuration pattern. The builder methods are the primary fluent API, but the existence of the specific Extension type suggests a lower-level or alternative registration path that duplicates the intent of 'adding localization support'.
- Low XML-doc coverage: TodoApp.Application (samples/TodoApp.Application/TodoApp.Application.csproj)
- Low XML-doc coverage: TodoApp.Domain (samples/TodoApp.Domain/TodoApp.Domain.csproj)
- Low XML-doc coverage: TodoApp.Infrastructure (samples/TodoApp.Infrastructure/TodoApp.Infrastructure.csproj)
- Low XML-doc coverage: TodoApp.Web (samples/TodoApp.Web/TodoApp.Web.csproj)
- Redundant abstraction: IRepository<TEntity, Tkey> defines the exact same method signatures as RepositoryBase<TDbContext, TEntity, Tkey>. In many DDD implementations, the Repository interface is the primary contract, and the Base class implements it. However, exposing both the Base class and the Interface with identical method names (GetAsync, GetAllAsync, etc.) suggests the Interface is redundant or the Base class should not be public if it's just an implementation detail of the interface.
- XML-doc coverage: Dddify (src/Dddify/Dddify.csproj)
- redundant comment (samples/TodoApp.Web/Program.cs)
- redundant comment (samples/TodoApp.Web/Program.cs)
- redundant comment (src/Dddify/Localization/Internal/JsonStringManager.cs)
- samples: 4 contract type(s) expose producer-owned ids/enums
Architecture
- Unchanged — 1 containers · 2 contexts · 1 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
esofar/dddify was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 1e4c046022a43e458b69c2307abb248859551384 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.