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
I want to process a json schema that includes a reference like:
$ref: './filename.json#/'
As far as I understood (and I ask for confirmation) this should be equivalent to the syntax:
$ref: './filename.json#'
where the final "/" is missing. Both of them should refer to the root element in the file "filename.json". But while the library properly process the second refernece, it fails to procvess the first one.
In the first case it think that that the json pointer inside of the file "filename.json" is not empty, and thus attempts to find a keyword that matches what is after the /, that is the empty string. and does not find such an empty keyword.
If my assumption that both references are correct, is the issue in the jsonschema library or in the jsonpointer library that processes "/" as a non empty json pointer? If you provide me some guidance, I can develop a merge request.
The text was updated successfully, but these errors were encountered:
I want to process a json schema that includes a reference like:
As far as I understood (and I ask for confirmation) this should be equivalent to the syntax:
where the final "/" is missing. Both of them should refer to the root element in the file "filename.json". But while the library properly process the second refernece, it fails to procvess the first one.
In the first case it think that that the json pointer inside of the file "filename.json" is not empty, and thus attempts to find a keyword that matches what is after the /, that is the empty string. and does not find such an empty keyword.
If my assumption that both references are correct, is the issue in the jsonschema library or in the jsonpointer library that processes "/" as a non empty json pointer? If you provide me some guidance, I can develop a merge request.
The text was updated successfully, but these errors were encountered: