Spell a reference path as arm.isRefPath, and say where each tail's head is held
This commit is contained in:
@@ -56,9 +56,7 @@ This round, in order:
|
||||
which differs from the `pathCheck` type it wraps by word order alone: both architects
|
||||
placed them wrong.
|
||||
- Correct the claims readers followed wrong: `IsTemplate`'s doc says an argument holding
|
||||
a bracket that is not valid JSON errors, where `misc.territory[SE]` is a path; `arm`'s
|
||||
says a tail's head is drawn once per expansion, where a reference path is held per
|
||||
render; the README says rows are indexed on the first draw, where `New` builds the key
|
||||
a bracket that is not valid JSON errors, where `misc.territory[SE]` is a path; the README says rows are indexed on the first draw, where `New` builds the key
|
||||
map; and `loadDir`'s says it builds the tree deterministically, where it reports an
|
||||
unnamed rows file in map order.
|
||||
- Delete the comments the panel found restating their code or arranging the file:
|
||||
|
||||
Reference in New Issue
Block a user