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
We use the jsonschema module to validate messages against our schemas.
At least in the manner we currently utilise it some of the messages for failed validation aren't as useful as they could be.
e.g. if someone attempts to send data containing a key that the schema has tagged 'disallowed', then the reported error is something like:
"[<ValidationError: "{'type': ['array', 'boolean', 'integer', 'number', 'null', 'object', 'string']} is not allowed for 'BadVALUE'">]
which is citing the value of the disallowed key when it would be more useful to cite the name of the key.
Hopefully, certainly in whatever version is current for python 3.9+, we can improve on this. If needs be we can investigate any alternative modules for validation.
The text was updated successfully, but these errors were encountered:
We use the
jsonschema
module to validate messages against our schemas.At least in the manner we currently utilise it some of the messages for failed validation aren't as useful as they could be.
e.g. if someone attempts to send data containing a key that the schema has tagged 'disallowed', then the reported error is something like:
which is citing the value of the disallowed key when it would be more useful to cite the name of the key.
Hopefully, certainly in whatever version is current for python 3.9+, we can improve on this. If needs be we can investigate any alternative modules for validation.
The text was updated successfully, but these errors were encountered: