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
It seems the bundling correctly adds the $defs section to the schema being bundled. However, when the referenced schema id is a full URI, it leads to reference names containing invalid characters such as : and /. Also, the original $ref occurrences in the original schema are not updated with the local reference.
The text was updated successfully, but these errors were encountered:
The original $refs are not supposed to be updated. When a compliant JSON Schema implementation sees the bundled schema, it first considers all $ids across the various embedded resources and pre-populates its internal cache
However, when the referenced schema id is a full URI, it leads to reference names containing invalid characters such as : and /
Are you referring to the property names in $defs? If so, that's OK. There is no limitation on the characters that can happen there and : and / are totally valid as per the JSON grammar!
Do you have an example that is incorrectly bundled and does not work?
But note that we only support that for problematic implementations. Compliant ones should work just fine with the normal approach. Let me know if that helped!
It seems the bundling correctly adds the
$defs
section to the schema being bundled. However, when the referenced schema id is a full URI, it leads to reference names containing invalid characters such as:
and/
. Also, the original$ref
occurrences in the original schema are not updated with the local reference.The text was updated successfully, but these errors were encountered: