Schemas can be reference using identifiers declared with $id and id. These identifiers need to be unique, but it's possible for a users to create two schemas with the same identifier. In these cases, we need to show an error on the $id/id keyword showing the user that there is a duplicate. There should also be a warning on the $schema keyword for any JSON document that references a schema with this conflict. We also need to make sure that the cache is properly invalidated in these cases.
One case to keep in mind is that identifiers could conflict with built-in meta-schemas, not just schemas within the workspace.
We'll need to handle any case where a schema can't be registered, not just the duplicate identifier case.
Schemas can be reference using identifiers declared with
$idandid. These identifiers need to be unique, but it's possible for a users to create two schemas with the same identifier. In these cases, we need to show an error on the$id/idkeyword showing the user that there is a duplicate. There should also be a warning on the$schemakeyword for any JSON document that references a schema with this conflict. We also need to make sure that the cache is properly invalidated in these cases.One case to keep in mind is that identifiers could conflict with built-in meta-schemas, not just schemas within the workspace.
We'll need to handle any case where a schema can't be registered, not just the duplicate identifier case.