Conversation
Signed-off-by: itvi-1234 <rjsumit71@gmail.com>
Preview Deployed!
Last updated at 2026-07-27T18:26:33Z |
AgniveshChaubey
left a comment
AgniveshChaubey
left a comment
There was a problem hiding this comment.
Also, right now, defs nodes are processed at the very beginning, which is why the defs keywords in the parent node and the defs-related child nodes are rendered first. We'll need to figure out a way to place them in the bottom half of the canvas even though they're processed early. We have to also keep in mind that on the backend, processing defs nodes early on is required, because they'll be referenced by other nodes later. We just need to adjust the placement of the defs keywords in parent node and defs nodes on canvas.
| } | ||
| return { key: "$defs", data: { value: shortNames.map(n => `def-${n}`) } } | ||
| }, | ||
| "https://json-schema.org/keyword/$defs": (ast, keywordValue, nodes, edges, parentId, nodeDepth, renderedNodes) => { |
There was a problem hiding this comment.
do we really need https://json-schema.org/keyword/$defs handler if we dont want to render a separate $defs node?
This branch was successfully deployed
2 participants
Uh oh!
There was an error while loading. Please reload this page.