Repository navigation
fix(deed): carry the registry's v8 id in identity fields (ruling g) #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,8 +17,8 @@ | |
| (repo-deed | ||
| :schema-version "1.0.0" | ||
| :canonical-name "xmlpull-zig" | ||
| :beholding-chora #u5"estate/chora" | ||
| :repo-uuid #u5"github.com/hyperpolymath/xmlpull-zig" | ||
| :beholding-chora #u8"chora:estate/github.com/hyperpolymath" | ||
| :repo-uuid #u8"gv-clade-index:github.com/hyperpolymath/xmlpull-zig" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Changing Useful? React with 👍 / 👎.
Comment on lines
+20
to
+21
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Keep the required deed literal format. Both fields now use As per coding guidelines, “In deed files use
|
||
| ; The canon pin: which release of hyperpolymath/standards canon.lock this | ||
| ; repo implements. It is the ONLY canon pin in this deed (deed_canon | ||
| ; refuses zero or two); the (rsr-profile) clause below declares | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When any consumer reads this field through
scripts/deed-field.sh --uuid, the parser discards the#u8tag and unconditionally passes the new string touuid5_url; it therefore emits the UUIDv512f79705-0c45-527e-b7d9-2369b7627921, not a UUIDv8 registry identity. This affects both arrival-pack and coaptation extraction, so the change does not actually carry the registry's v8 ID through the repository's supported reader; update the reader for#u8semantics alongside this field.Useful? React with 👍 / 👎.