Compiling a subresource with an extension validates the subresource against the root extension schema. about jsonschema HOT 6 CLOSED

If you can share the complete source code, and some example of what your extension is trying to do, then it would help me understand your issue.

from jsonschema.

I've created a fork and committed an example you can run with go test, see openapi_test.go:

https://github.com/dan-j/santhosh-tekuri-jsonschema/tree/142-extension-subschema-validation

from jsonschema.

Updated with some comments ^

from jsonschema.

I had a look at your source code; it seems you got confused "what is meant by extension"

openapi document is a json document. and its jsonschema is openapi_3.1.schema.json (note that you are confused that openapi_3.1.schema.json is the schema of extension. no it is not)

openapi uses jsonschema to specify schema for request and responses. but in addition to standard jsonschema it includes few additional keywords discriminator, xml, externalDocs and example (see Fixed Fields section in https://spec.openapis.org/oas/v3.1.0#schema-object)

among the above 4 keywords, only discriminator effects validation. rest of them are just for documentation purpose

so you have to write an extension for discriminator keyword. and the schema for this is at https://spec.openapis.org/oas/3.1/meta/base

now if you want to understand why you are getting validation error in your specific implementation:
you created an extension whose schema is openapi_3.1.schema.json. and openapi_3.1.schema.json says, openapi and info are required. So when you use this extension you are saying: I am introducing two new keywords openapi and info which are mandatory. So you are getting validation errors in schema compilation.

from jsonschema.

Ahh ok. So I was under the impression that extensions would only be applied if the ExtCompiler returned an ExtSchema, which for the full spec, it contains "openapi" so I return a noop schema, but for others I am returning nil.

I'm going to close this, thanks for your response!

from jsonschema.

extensions are always applied.

that mean your schema must be valid against all the registered extensions.
the extension.validate implement should look for its keywords and do the validation logic

from jsonschema.