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
HttpApi layer, including the resolve-path endpoint #5
REST controllers / conventional API surface for page, content type, field and content management.
The resolve-path contract from design doc §7.4: resolve-path(path) -> { matched, page, content, contentType }. SiteRouteResolver already implements the resolution and returns a RouteMatch; this is the HTTP projection of it, and is what a Tier 1 (out-of-process) front end consumes.
Swagger / OpenAPI surface.
Note on naming
ABP's conventional controllers derive the route from the method name, not from an attribute route template. A GetListAsync and a CreateAsync collide on the same URL regardless of any [HttpPost("...")] attribute. Name search-style POST endpoints accordingly (SearchAsync, not GetListAsync).
Done in 92c9b31 (on top of the HttpApi work already landed in 33c8cfd for #4).
REST controllers for page/content-type/field/content management: explicit Admin/Public controllers (not Auto API Controllers - see the naming note below), landed with Application and Application.Contracts layer for the content kernel #4's HttpApi follow-up. Swagger/OpenAPI surface confirmed working there too.
resolve-path contract (§7.4): GET /api/site-public/resolve-path?Path=...&CultureName=... -> { matched, kind, page, content, contentType }, a thin HTTP projection of SiteRouteResolver.ResolveAsync (unmodified). Public-only, includeUnpublished hardcoded false. RouteMatchKindDto mirrors the domain's RouteMatchKind locally.
On the naming note: sidestepped rather than worked around - the controllers use explicit [Route]/[Http*] attributes per action (CmsKit's pattern), not ABP's conventional/Auto API Controllers, so there's no method-name-derived route to collide on in the first place.
127 tests passing (57 domain + 70 EF Core/application integration).
Activity
Add the resolve-path endpoint (#5)
duguankui commentedon Aug 4, 2026
Done in 92c9b31 (on top of the HttpApi work already landed in 33c8cfd for #4).
resolve-pathcontract (§7.4):GET /api/site-public/resolve-path?Path=...&CultureName=...->{ matched, kind, page, content, contentType }, a thin HTTP projection ofSiteRouteResolver.ResolveAsync(unmodified). Public-only,includeUnpublishedhardcoded false.RouteMatchKindDtomirrors the domain'sRouteMatchKindlocally.On the naming note: sidestepped rather than worked around - the controllers use explicit
[Route]/[Http*]attributes per action (CmsKit's pattern), not ABP's conventional/Auto API Controllers, so there's no method-name-derived route to collide on in the first place.127 tests passing (57 domain + 70 EF Core/application integration).