on master help sign in
Review: add links to validators
56c902cYaseen
userspace/graph-store/validator-walkthrough.md+8−6
@@ -32,7 +32,7 @@ The graph represents a chat channel and contains all chat messages in order. A c
32
32
33
33
34Here's the definition of the schema in the chat validator mark:
34Here's the definition of the schema in the chat validator mark:
35−File: `mar/graph/validator/chat.hoon`
35+File: [`mar/graph/validator/chat.hoon`](https://github.com/urbit/urbit/blob/fbd85abf4e41d580654606a6defb764f6a97256d/pkg/arvo/mar/graph/validator/chat.hoon#L33-L40)
36```
36```
37++ grab
37++ grab
38 |%
38 |%
@@ -76,7 +76,7 @@ For example, it wouldn't make sense to give readers `%self`, because they do not
76
76
77Let's see how this permissioning system is implemented in the validator code.
77Let's see how this permissioning system is implemented in the validator code.
78
78
79−Here is the `grow` arm of `mar/validator/chat.hoon`
79+Here is the `grow` arm of [`mar/validator/chat.hoon`](https://github.com/urbit/urbit/blob/fbd85abf4e41d580654606a6defb764f6a97256d/pkg/arvo/mar/graph/validator/chat.hoon#L7-L20)
80```
80```
81|_ i=indexed-post :: A
81|_ i=indexed-post :: A
82++ grow
82++ grow
@@ -131,7 +131,7 @@ The root graph represents the whole Links collection. Every Links entry is a chi
131The comments section holds all individual comment nodes, but comments are not simple leaf nodes. An individual comment is actually a structural node that acts as a revision container, storing the comment's full edit history by storing each edit as a child node. The front-end is responsible for properly displaying the latest revision of the comment.
131The comments section holds all individual comment nodes, but comments are not simple leaf nodes. An individual comment is actually a structural node that acts as a revision container, storing the comment's full edit history by storing each edit as a child node. The front-end is responsible for properly displaying the latest revision of the comment.
132
132
133
133
134−Here's the validator, located at `mar/graph/validator/link.hoon`:
134+Here's the validator, located at [`mar/graph/validator/link.hoon`](https://github.com/urbit/urbit/blob/fbd85abf4e41d580654606a6defb764f6a97256d/pkg/arvo/mar/graph/validator/link.hoon#L49-L73):
135```
135```
136++ grab
136++ grab
137 |%
137 |%
@@ -198,7 +198,7 @@ Let's analyze the permissions structure.
198
198
199**TODO** *stubbed out awaiting potential changes in source*
199**TODO** *stubbed out awaiting potential changes in source*
200
200
201−Here's how it is implemented:
201+Here's how it is implemented [(source)](https://github.com/urbit/urbit/blob/master/pkg/arvo/mar/graph/validator/link.hoon#L2-L27):
202
202
203```
203```
204|_ i=indexed-post
204|_ i=indexed-post
@@ -286,7 +286,7 @@ Here's how it is implemented:
286
286
287Here, a notebook, which is a collection of blog posts (called notes), is represented by the root graph. All data associated with the blog post is represented by the top level node, which is the note itself along with the associated comments. One level deeper, we see two container structures. The first one is the post revision container; it holds the edit history of your blog post. Every child node of this corresponds to the actual title and text of your blog post. The second one is the comments container. This represents the comment section of your blog post. Every child node of this is not a comment, but a comment revision container, which, as before, contains the edit history of your comment.
287Here, a notebook, which is a collection of blog posts (called notes), is represented by the root graph. All data associated with the blog post is represented by the top level node, which is the note itself along with the associated comments. One level deeper, we see two container structures. The first one is the post revision container; it holds the edit history of your blog post. Every child node of this corresponds to the actual title and text of your blog post. The second one is the comments container. This represents the comment section of your blog post. Every child node of this is not a comment, but a comment revision container, which, as before, contains the edit history of your comment.
288
288
289−Here's its validator
289+Here's its validator, located at [`mar/graph/validator.hoon`](https://github.com/urbit/urbit/blob/master/pkg/arvo/mar/graph/validator/publish.hoon#L56-L97)
290```
290```
291 ++ noun
291 ++ noun
292 |= p=* :: 1
292 |= p=* :: 1
@@ -374,10 +374,12 @@ Notably, the revision container for the blog post itself allows the post to be e
374 <img src="images/image14.png"/>
374 <img src="images/image14.png"/>
375</p>
375</p>
376
376
377−Let's take a look at the permissioning structure for Publish.
377+Let's take a look at the permissioning structure for Publish.
378
378
379**TODO** *stubbed out awaiting potential changes in source*
379**TODO** *stubbed out awaiting potential changes in source*
380
380
381+[(source)](https://github.com/urbit/urbit/blob/fbd85abf4e41d580654606a6defb764f6a97256d/pkg/arvo/mar/graph/validator/publish.hoon#L6-L24)
382+
381```
383```
382|_ i=indexed-post
384|_ i=indexed-post
383++ grow
385++ grow