issue - speced/respec GitHub Wiki
Marks content as an open issue box. When used with github, can automatically embed a GitHub issue by number.
<div class="issue">
<p>We need to decide whether this should be synchronous.</p>
</div><div class="issue" data-number="363"></div><p class="issue" title="Needs resolution">
Should this be normative?
</p><div class="issue atrisk" data-number="42">
<p>This feature may be removed before publication.</p>
</div>Adding class="atrisk" alongside class="issue" renders the heading as "(Feature at Risk) Issue N" — the W3C Process convention for marking features under review during CR.
When atRiskBase is configured, data-number links to that tracker instead of issueBase:
var respecConfig = {
issueBase: "https://github.com/example/repo/issues/",
atRiskBase: "https://github.com/example/repo/issues/",
};- When
data-numberis set andgithubis configured, ReSpec downloads the issue content from GitHub and embeds it - GitHub issues with
state: "CLOSED"render with aclosedCSS class - The
titleattribute is interpreted as HTML — seetitleattributes - Works inline:
<span class="issue">…</span>renders as a compact inline issue marker - Use
issue-summaryto generate a collected list of all issues in the document - Issues are numbered automatically (e.g. "Issue 1", "Issue 2")