dcdpr / jp / 26892836545
67%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 402
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.57%. Remained the same
26892836545

push

github

web-flow 
docs(rfd): Publish draft RFDs on the website (#734)

Draft RFDs lived under `docs/rfd/drafts/` but were excluded from the
VitePress build (`srcExclude: ['rfd/drafts/**']`), making them only
reachable on GitHub. This commit brings them onto the website at
`/rfd/drafts/`.

A new `rfd-drafts.data.js` loader mirrors the published loader but with
relaxed severity: duplicate ids still abort the build, while
relationship and cycle problems only warn (drafts are a work in
progress). Summaries and the stray-draft-reference rule don't apply to
drafts at all.

The shared parsing and validation logic previously embedded in
`rfds.data.js` is extracted into `rfd-shared.js` so both loaders can use
the same `parseMeta`, `parseReferences`, `buildEntries`, `buildGraph`,
and the five check functions. The published loader is now a thin wrapper
around those helpers.

A new `RfdIndex.vue` component replaces the ~250-line inline
table/filter block that lived directly in `docs/rfd/index.md`. It
accepts `entries`, `showStatus`, and `storageKey` props, so the drafts
index page can reuse it with `show-status="false"`.

The four RFD theme components (`RfdBreadcrumb`, `RfdLinkColors`,
`RfdReferences`, `RfdIndex`) are updated to merge published and draft
data, and their path regexes now handle the extra `drafts/` segment.

Relative links in all draft files are corrected: they previously used
sibling-relative paths (e.g. `065-foo.md`) that failed to resolve since
drafts live in a subdirectory. They now use parent-relative paths
(`../065-foo.md`), and links to source files gain an extra `../` level
to account for the deeper directory.

The `rfd-promote` justfile recipe is extended to strip `../` from both
inline links and reference definitions when a draft is promoted, so no
manual fixup is needed after promotion.

Three infrastructure additions keep the raw-`.md` serving story
consistent: a `serveMarkdownAsUtf8` Vite plugin forces `charset=utf-8`
on dev-server responses (browsers d... (continued)

33676 of 50587 relevant lines covered (66.57%)

266.79 hits per line

Jobs
ID Job ID Ran Files Coverage
1 26892836545.1 402
66.57
 GitHub Action Run
Source Files on build 26892836545