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
The "human views" of a JSON Schema may include "author" $comment fields on any object.
This may be used to document changes between 2 version or explain the exact purposes of fields for instance.
E.g.
"someObject": {
"$comment": "This was changed into a string to allow internal references which are not an URI. Having an additional field was rejected because [...].",
"type": "string",
}
Therefore it would be useful to display the value of $comment fields in the generated docs, possibly activated with a specific option.
The text was updated successfully, but these errors were encountered:
The "human views" of a JSON Schema may include "author"
$comment
fields on any object.This may be used to document changes between 2 version or explain the exact purposes of fields for instance.
E.g.
Therefore it would be useful to display the value of
$comment
fields in the generated docs, possibly activated with a specific option.The text was updated successfully, but these errors were encountered: