Expand description
Server-rendered HTML views — zero framework, inline CSS, every
interpolation passed through crate::request::esc.
There is no templating engine and no client-side JS in the rendered
markup: the forge is server-rendered by construction, and the XSS
spine is content-type + esc() (see crate::request).
Functions§
- blob_
page - A blob (file) view.
contentisSome(text)for a textual blob orNonefor a binary one (a download link is shown instead). - commit_
page - Single-commit view: metadata + the unified-diff patch in a
<pre>. - commits_
page - Paginated commit log view.
- crumbs
- Render a breadcrumb nav bar from
(label, href)pairs. The last entry is rendered as plain (non-link) text. - index_
page - The global landing page listing
(owner, repo)pairs. Each row links to the repo overview. An empty list renders an explanatory note. - issue_
detail_ page - A single issue thread view: title/state header plus each re-fetched
body.
truncatedwarns when the thread exceeded the read cap. - issue_
new_ page - The new-issue form. The body document is PUT to the author’s pod by
the client first; this form submits the resulting
resourceUrlpointer plus a title. (Podless agents submit the body inline — Tier 2.5.) Server-rendered, no script. - issues_
list_ page - The issues list, with an open/closed filter and a “new issue” link.
- owner_
page - A single owner’s repo list.
- page
- Wrap
body_htmlin a full HTML document with a shared header and the inline stylesheet.titleis escaped;body_htmlmust already be composed ofesc()’d values. - refs_
page - A ref list (branches or tags).
link_verbis"commits"for branches (link to the branch log) or"tree"for tags. - repo_
overview_ page - Repo overview: header, root tree at
rev, and an optional README. - tree_
page - A subdirectory listing view.