Skip to content

HttpApi layer, including the resolve-path endpoint #5

Closed

Description

@duguankui

Depends on #4 (Application layer).

Scope

  • 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).

References

  • src/Dignite.Sites.Domain/Routing/SiteRouteResolver.cs
  • Design doc §7.4

Activity

  1. added this to the P0 Content kernel milestone on Aug 4, 2026
  2. added
    phase: P0Content kernel - landed, these are follow-ups
    group: 1-interfaceApplication + HttpApi - the gate everything downstream waits on
    on Aug 4, 2026
  3. added a commit that references this issue on Aug 4, 2026
  4. duguankui commented on Aug 4, 2026

    @duguankui
    MemberAuthor

    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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: content-kernelPage / ContentType / Content / Fieldgroup: 1-interfaceApplication + HttpApi - the gate everything downstream waits onphase: P0Content kernel - landed, these are follow-ups

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions