-
-
Notifications
You must be signed in to change notification settings - Fork 586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative $refs crash when $id is a URN or other custom scheme #544
Labels
Bug
Something doesn't work the way it should.
Needs Test Upstream
Issues that need to have a test added to https://github.com/json-schema-org/JSON-Schema-Test-Suite
Comments
OrangeTux
pushed a commit
to mobilityhouse/ocpp
that referenced
this issue
Oct 28, 2019
jsonschemas has a bug with parsing $refs if the schema's $id is a URN[1]. It basically fails to load the schema. We don't need the $id. Therefore al $id's have been removed. [1]: python-jsonschema/jsonschema#544
OrangeTux
pushed a commit
to mobilityhouse/ocpp
that referenced
this issue
Oct 28, 2019
jsonschemas has a bug with parsing $refs if the schema's $id is a URN[1]. It basically fails to load the schema. We don't need the $id. Therefore al $id's have been removed. [1]: python-jsonschema/jsonschema#544
OrangeTux
pushed a commit
to mobilityhouse/ocpp
that referenced
this issue
Oct 29, 2019
jsonschemas has a bug with parsing $refs if the schema's $id is a URN[1]. It basically fails to load the schema. We don't need the $id. Therefore al $id's have been removed. [1]: python-jsonschema/jsonschema#544
OrangeTux
pushed a commit
to mobilityhouse/ocpp
that referenced
this issue
Oct 29, 2019
jsonschemas has a bug with parsing $refs if the schema's $id is a URN[1]. It basically fails to load the schema. We don't need the $id. Therefore al $id's have been removed. [1]: python-jsonschema/jsonschema#544
OrangeTux
pushed a commit
to mobilityhouse/ocpp
that referenced
this issue
Oct 29, 2019
jsonschemas has a bug with parsing $refs if the schema's $id is a URN[1]. It basically fails to load the schema. We don't need the $id. Therefore al $id's have been removed. [1]: python-jsonschema/jsonschema#544
OrangeTux
pushed a commit
to mobilityhouse/ocpp
that referenced
this issue
Oct 29, 2019
jsonschemas has a bug with parsing $refs if the schema's $id is a URN[1]. It basically fails to load the schema. We don't need the $id. Therefore al $id's have been removed. [1]: python-jsonschema/jsonschema#544
Julian
added a commit
that referenced
this issue
Apr 29, 2022
060caae0d Merge pull request #467 from gene-hightower/strict-rfc-grammar 995932c74 Additional RFC-5321 Mailbox tests 637f0ac3e Merge pull request #542 from jdesrosiers/dyanmicref-no-bookending 87944e52e Merge pull request #543 from jdesrosiers/update-vocabulary-for-draft-next 07b90e3b5 Merge pull request #544 from frawa/list-typed-json 365349adc list typed-json in new Scala section 9d1efc27e Update vocabulary tests for draft-next 89f59caad Update dynamicRef tests for bookenending removal git-subtree-dir: json git-subtree-split: 060caae0dd58e34af0449baec1103606a0ef4977
RoaringDev1203
added a commit
to RoaringDev1203/Cratus-OCPP
that referenced
this issue
Aug 27, 2024
jsonschemas has a bug with parsing $refs if the schema's $id is a URN[1]. It basically fails to load the schema. We don't need the $id. Therefore al $id's have been removed. [1]: python-jsonschema/jsonschema#544
ajmirsky
pushed a commit
to ajmirsky/ocpp
that referenced
this issue
Nov 26, 2024
jsonschemas has a bug with parsing $refs if the schema's $id is a URN[1]. It basically fails to load the schema. We don't need the $id. Therefore al $id's have been removed. [1]: python-jsonschema/jsonschema#544
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
Something doesn't work the way it should.
Needs Test Upstream
Issues that need to have a test added to https://github.com/json-schema-org/JSON-Schema-Test-Suite
Using a URN for the $id property in a schema is causing many URL related errors:
This is possibly a duplicate of #313, but I cannot reproduce this without a URN $id.
Schema:
The text was updated successfully, but these errors were encountered: