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
Since Apikana now creates schema draft7 it replaces the id with $id and now the validation fails when using references inside definitions that use $id. However, the JSON schema itself is actually valid, but it seems that ajv is not able to compile it properly.
If I remove the $id from the schema, it works as usual. But I don't think that's a good approach, especially since Apikana creates the JSON schema using $id now.
The text was updated successfully, but these errors were encountered:
Since Apikana now creates schema draft7 it replaces the id with $id and now the validation fails when using references inside definitions that use $id. However, the JSON schema itself is actually valid, but it seems that ajv is not able to compile it properly.
Here is an example schema:
It validates without any error on JSON Schema Validator but when using ajv, it fails with this error:
If I remove the
$id
from the schema, it works as usual. But I don't think that's a good approach, especially since Apikana creates the JSON schema using$id
now.The text was updated successfully, but these errors were encountered: