Repository navigation
Keep every Draft 3 graph form edge inside the document - #1148
Conversation
An edge of the graph stood for any subschema that was nothing but a reference, including one whose target lived in another document. Such an edge could not reach an entry, so the reference it carried had to be written back into every body that reached it, and the form admitted edges that were not edges of the graph at all. An edge is now only a reference that stays in the document. One that leaves it becomes an entry of its own, so every edge points at `#/definitions/<integer>` and the special case for carrying a foreign URI back into the bodies goes away. The metaschema says so too: `entry` and `edge` had the same shape and are now one definition, and `definitions` must hold at least one entry, since the wrapper always points at one. Signed-off-by: Vansh <officialbusiness9818@gmail.com>
🤖 Augment PR SummarySummary: Keep Draft 3 canonical graph edges inside the document. 🤖 Was this summary useful? React with 👍 or 👎 |
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
|
pre-requisite to #1140 |
|
awesome! |
2 participants
An edge of the graph stood for any subschema that was nothing but a reference, including one whose target lived in another document. Such an edge could not reach an entry, so the reference it carried had to be written back into every body that reached it, and the form admitted edges that were not edges of the graph at all.
An edge is now only a reference that stays in the document. One that leaves it becomes an entry of its own, so every edge points at
#/definitions/<integer>and the special case for carrying a foreign URI back into the bodies goes away.The metaschema says so too:
entryandedgehad the same shape and are now one definition, anddefinitionsmust hold at least one entry, since the wrapper always points at one.