You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Application and Application.Contracts layer for the content kernel #4
P0 delivered the Domain and EntityFrameworkCore layers. The Dignite.Sites.Application / .Application.Contracts projects (and the Admin / Public / Common variants) are still template scaffold.
Scope
DTOs for Page, ContentType (including its field arrangement), Field, FieldGroup, Content.
Application services wrapping the existing domain managers — PageManager, ContentTypeManager, FieldManager, ContentManager — which already hold the invariants, so the app layer should stay thin.
Permission definitions and checks.
Object mapping (the solution is set up for Mapperly).
A DTO shape for flex field values that round-trips the value bag without leaking FlexFieldDictionary into the contract.
Watch out for
A content's field values arrive as a loose IDictionary<string, object?>. ContentManager already drops keys the content type does not declare, and validation already runs through the field types. The app layer should not duplicate either.
The field rename flow has a mandatory ordering (see FieldManager.RenameAsync). App services must go through the manager and never touch Field.SetName directly, or every stored value for that field becomes unreachable.
Common.Application.Contracts: read DTOs for Page/ContentType(+field arrangement)/Field/FieldGroup/Content, shared between Admin and Public.
Admin.Application(.Contracts): write DTOs, full CRUD services, permissions. Field rename is its own endpoint/permission (data migration, not a property edit). ContentType delete is guarded against contents still using it.
Public.Application(.Contracts): read-only, Page limited to active, Content limited to published-as-of-now. No FieldGroup (admin-only concept).
Flex-field value DTO is a plain IDictionary<string, object?>, same shape on read and write, so a GET's FieldValues posts straight back through an UPDATE unchanged.
Mapperly mappers per module (ABP's per-module DI scanning doesn't share across assemblies); dictionary/value-object conversions hand-written in Common.Application.
Explicit Admin/Public HttpApi controllers (not Auto API Controllers) under /api/site-admin/... and /api/site-public/...; Host wired to the unified Application + HttpApi modules.
122 tests passing (57 domain + 65 EF Core/application integration, including round-trip, rename-migration, delete-guard and flex-field-query-condition coverage).
Activity
Add Application layer for the content kernel, expose it over HTTP (#4)
duguankui commentedon Aug 4, 2026
Done in 33c8cfd.
IDictionary<string, object?>, same shape on read and write, so a GET's FieldValues posts straight back through an UPDATE unchanged./api/site-admin/...and/api/site-public/...; Host wired to the unified Application + HttpApi modules.Add the resolve-path endpoint (#5)
Drop the spent codex-prompts runbook, refresh design doc progress note