ajv-formats | JSON Schema format validation for Ajv v8+ | JSON Processing library

According to this issue Typescript must be ran in strict mode to transpile the code correctly. Seems Objection v3 is still in some pre-release state so this isn't quite documented yet.

I got it ! I add below code to my angular.json file.

Ok I got it, the directory in which the script was run was actually /home/runner/work/schema_randonnee/schema_randonnee/ (visible in the workflow logs of the actions/checkout@v2 run). So by adding /home/runner/work/schema_randonnee/schema_randonnee/GeoJSON_schemas/ before all my input values (main_schema_path, additional_schemas_dir and data_path), the script managed to reach the files in the workflow repo!

The action checkout@v2 checks out the repository under $GITHUB_WORKSPACE (cf. README) and this env value is defined by default on /home/runner/work/my-repo-name/my-repo-name as visible in this GitHub doc. Without changement on the run of that checkout action, it's the directory to indicate to the GitHub Action you're calling (which is by default running at the same level than /home if I understand well).

Edit: even better than the previous solution, I should use the generated$GITHUB_WORKSPACE variable that way:

fast-json-stringify does the serialization, not the validation.

The json schema provided to it will be used to serialize only the properties declared and some type checking like integer or arrays.

• the enum keyword is not supported
• the format keyword is supported only for the dates as documented:

To reach your goal, you should use this plugin: fastify-response-validation that will add a validation step of your response body before the serialization process.

Your intuition is correct, the $ref isn't resolving as you expect because of the $id. $refs are resolved against the $id of the schema. In this case, { "$ref": "#/definitions/person" } is resolved against "$id": "http://asite.org/schemas/member.json" resulting in http://asite.org/schemas/member.json#/definitions/person which doesn't exist. The solution is to use the $id of the person schema rather than a relative path: { "$ref": "person.json" }.

As an aside, you might prefer the alternate API for compiling schemas that works better when dealing with bundled schemas like your "definitions.json". You can load the whole file and then compile the individual schemas you want by their $id.