radicle/rips
1
0
Fork 0
mirror of https://seed.radicle.dev/rad:z3trNYnLWS11cJWC6BbxDs5niGo82.git synced 2026-10-18 19:10:39 +08:00
Code Issues Packages Projects Releases Wiki Activity

0004: Fix broken cross-references

Browse Source 
A natural cross-reference matches a section title exactly, including its
case, and Asciidoctor emits the target text as a literal anchor when it
cannot match. Four references therefore pointed at anchors that do not
exist, which is silent in the source and only shows up once the document
is rendered and its links are checked.

Correct the case of "The repository", "The authority" and
"Future work" to match the sections they refer to.

Join the reference `<<The Query,query>>` that was split across a line
break, which made it resolve to "TheQuery".
This commit is contained in:
Daniel Norman
2026-08-14 14:02:45 +02:00
committed by Lorenz Leutgeb
parent 7393561890
commit b7d0548c81
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
0004-general-uri-scheme/general-uri-scheme.adoc
+7 -7
View File
@@ -336,9 +336,9 @@ include::data/test/tc05[]
==== The Resource Type and Identity
While <<The repository,the repository>> allows you to refer to a Git repository,
While <<The Repository,the repository>> allows you to refer to a Git repository,
it may also be desirable to refer to one or more specific resources within
that repository. To do this, <<The repository,the repository>> may be followed
that repository. To do this, <<The Repository,the repository>> may be followed
by a "/", a resource type and identity.
By default, the resource type and identity is nothing, left to be added
@@ -435,8 +435,8 @@ parameters `tree`, `blob` and `path` to refine the `rad:` URI.
--
The identifier that follows this type must be a Git object identifier.
With this resource type, it makes no sense to use any of the <<The
Query,query>> defined above.
With this resource type, it makes no sense to use any of the
<<The Query,query>> defined above.
--
`tag`::
@@ -725,7 +725,7 @@ include::data/test/tc32[]
* Implementations may implement only part of this specification, depending on
what makes sense in the context of what they do. It is advisable, however, if
they can parse enough of a valid `rad:` URI to allow for <<Future work,future work>>.
they can parse enough of a valid `rad:` URI to allow for <<Future Work,future work>>.
For example, it is hard to imagine that `git-remote-rad` would ever support
more elaborate URLs than those involving an RID and an NID:
@@ -762,9 +762,9 @@ other patches in the same repository with `patch/{PATCH-ID}` or `issue/{ISSUE-ID
Future work may include:
* amending <<The authority,the authority>> with Radicle network
* amending <<The Authority,the authority>> with Radicle network
specification syntax (pending future formalization of that idea).
* amending <<The authority,the authority>> with multi-device IDs (also
* amending <<The Authority,the authority>> with multi-device IDs (also
pending formalization of that idea).
* adding more resource types, and their respective syntaxes
* extending existing resource types.