Bug fix: Policy templates field validation #125
Conversation
There was a problem hiding this comment.
This entire file feels like it contains functions that might come in handy for other Application Functions, such as the Data Collection AF. I'm wondering whether we should factor it out as a shared library that lives in rt-common-shared?
There was a problem hiding this comment.
Fine to do the additional JSON input parameter validation here. But would be good to move these validations into the autogenerated parsing code eventually. Maybe we create a backlog issue for that?
There was a problem hiding this comment.
Agreed, we need to look at getting the the validation in the templates to match regex's.
I'll raise a backlog ticket for that and another to look at handling the enumerated types with string catch-all better.
These fix issues with the validation of fields in the Policy Templates where the field type is a string restricted by a regex in the OpenAPI and fixes a bug in number range validation for integer types.
This addresses #120, #121, #122 and #124.