Added the 3 primitive json data types: Boolean, Number, String
To confirm this is working, you can take a look at ddf00013 in dev. I changed the rule to use boolean values instead of string "true"/"false". You will see 2 things:
The Load Test Datasets pane will show json booleans instead of strings:
When you load the negative test data, you will get 3 issues. In prod, you will not get these issues with boolean instead of string values in the rule.
Currently, I am using initcap types (Boolean, Number, String) because these are the types specified by the test data files. I would prefer if we use lowercase types (boolean, number, string), because this is how they are represented in json schema:
https://json-schema.org/draft/2020-12/json-schema-validation#section-6.1.1
But I understand this would require us to update the test data files, so let me know if you think we should do this.
Added the 3 primitive json data types: Boolean, Number, String To confirm this is working, you can take a look at ddf00013 in dev. I changed the rule to use boolean values instead of string "true"/"false". You will see 2 things:
The
Load Test Datasets
pane will show json booleans instead of strings:In prod, these are:
When you load the negative test data, you will get 3 issues. In prod, you will not get these issues with boolean instead of string values in the rule.
Currently, I am using initcap types (Boolean, Number, String) because these are the types specified by the test data files. I would prefer if we use lowercase types (boolean, number, string), because this is how they are represented in json schema: https://json-schema.org/draft/2020-12/json-schema-validation#section-6.1.1 But I understand this would require us to update the test data files, so let me know if you think we should do this.