Use a TypeChecker with JSONSchema rather than the types parameter

Before raising this MR, consider whether the following are required, and complete if so:

  • Unit tests
  • Metrics
  • Documentation update(s)

If not required, please explain in brief why not.

Description

This MR updates how we handle passing custom types to the schema validator. Previously we were using the legacy, deprecated approach of just passing a dict of types to the validator constructor. The supported approach (and only available approach in version 4.x) is to specify a custom TypeChecker instance when creating the validator class. This is the approach switched to in this MR.

The MR also removes the pin on the jsonschema version, since there's no need for it anymore.

Validation

Run tox -re server, and see everything working properly. You could modify data/config/default.yml to be an invalid config too to see the validation still working.

Issues addressed

Closes #382 (closed)

Merge request reports

Loading