You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the schemas that we support all come from the YAML spec, and specify generic types that may exist in a document. This means that for plain nodes in particular, implicit tags are assigned to values based on regexp pattern matches.
As a possible alternative, we could support something like JSON Schema instead, which would allow for defining a document-specific structural schema, which would permit for much greater type safety in our output.
This discussion was converted from issue #124 on December 11, 2020 12:24.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
At the moment, the schemas that we support all come from the YAML spec, and specify generic types that may exist in a document. This means that for plain nodes in particular, implicit tags are assigned to values based on regexp pattern matches.
As a possible alternative, we could support something like JSON Schema instead, which would allow for defining a document-specific structural schema, which would permit for much greater type safety in our output.
Beta Was this translation helpful? Give feedback.
All reactions