Very nice job, thank u!
tt67wq
tt67wq
itsok
ex_json_schema has a function resolve/1 which also does validation of the schema against it’s meta schema.
@ityonemo is there a built-in way to validate the schema against in meta schema in exonerate (I tried to find it but without success)? I’m basically fishing for ideas how to go about doing meta validations in the most sensible way. I’m thinking of having a mix task that will load the json schema, validate it and return errors if there are any. That way it will be a tiny bit easier to write the json schema before it is committed to a repo.
Any tips most welcome!
0
ityonemo
I don’t do this currently since I support multiple jsonschema versions at the same time, and some versions validate differently than others. I would recommend running through a validator first. But I could consider building it out.
0
Sebb
Hi, just tried that out, could be a great improvemend over ex_json_schema…
Have some questions.
- what is the function name I get from
function_from_file? - If I’m using a document like opneapi or asyncapi that has fragments of schemas all over the place and uses a lots of refs, how can I load the fragments and still automatically resolve the refs
- are refs to other files (in the fs) automatically resolved?
0
timothy
You specify it in the function arg, for example: function_from_file(:def, :validate, path_to_file) will generate the function validate/1.
0
Sebb
indeed, I was confused by
“The function names will contain the file url.”
and also
“generates a series of functions”
0
gmile
Is anyone using exonerate to validate HTTP request payloads? If so, how are you doing it?
I know there exists an apical library, but I cannot quite use it, since that would mean I need to replace my entire router, which is a big undertaking but also and kind of unusual thing to do…
0
pauldemarco
I’ve finally released my package that uses Exonerate under the hood, called auto_struct.
Thanks for the great lib @ityonemo !
0