Derek Holmes

Ability to ignore case related errors.

2

I would like the ability to ignore errors regarding casing. The problem is validating json with improper casing ie {Name:"Derek"} vs {name:"Derek"} generates the error "NoAdditionalPropertiesAllowed". This is the same...

RequiredAttribute trumps DefaultRequired settings

1

When using the generator: ``` var schemaGenerator = new JSchemaGenerator { DefaultRequired = Required.DisallowNull }; ``` Any model with the "Required" attribute on the model is forced to be "Required.Always"...

Left off, trying to find out why a child library has issues with Tasks

Feature/directionality

3

Added directionality checks for owasp-array-limit and owasp-string-limit. In the current description these are to limit resource exhaustion attacks which only make sense on the requests. https://github.com/daveshanley/vacuum/issues/667

Response vs Request directionality distinction

2

With both the owasp-array-limit and owasp-string-limit I would like separate severities depending on the direction. For example if a string doesn't have a limit on the request its much more...