Open tillias opened 3 years ago
This continues to be a problem and should be addressed. The problem is the underlying library being used does not support the newer version of the schema definition and does NOT plan on doing so. https://github.com/everit-org/json-schema/issues/441#issuecomment-949585872
If a customer comes with schemas using 2020-12, then using the product is a non-starter.
We're working on our own JSON schema library, since we did not find an existing one suitable for our needs. We'll make it a priority.
I've found a workaround is to use Draft 7 ("$schema": "https://json-schema.org/draft-07/schema"
). Of course then you can't use 2020-12 features but at least you can use apicurio.
Yeah - thanks @Mainstay-Noah-Huppert for updating this. The library we're currently using for this functionality does not support the most recent versions of JSON Schema. As @jsenko reported we have plans to write our own, but we have limited bandwidth for this activity at the moment.
Understood. Perhaps a quick win would be an initial submit validation for json schemas that looks at the version and provides feedback regarding support.
What’s weird about this is the error doesn’t manifest until after you attempt to upload a new version. This could put users into an awkward position as they won’t have any warning of the issues until possibly after the schema is being used in production.
Hi, I have run into a weird behaviour related to this issue. I have a global rule in registry to check FULL schema validity and if I try to upload a new version of json schema (2020-12), I get the same error as above. But what is strange - if I set schema validity rule on the artifact itself, the registration is suddenly working :) And it seems that the validation itself is working, at least for some json schema constructions (e.g. if I modify type string to string2, schema registry returns validation error).
Does it happen to anyone else as well? We are going to use it as a workaround - if a new json schema of version 2020-12 is registered, the validation rule has to be set explicitely on it and then everything seems to be working.
Hello folks,
I have version 1 of Artifact (JsonSchema) without timestamp field. Whenever I activate any compatibility rule and try uploading new version with optional timestamp I got exception:
Here is schema I'm using: