Feature : Restrictive / Lock down API specification

[LasneF]

do you think it would be possible to kind of lock down the spec
Kind of setting aditionnal Properties to false with a flag in wiretab command line

meanning given the spec
"schema" : {
"type" : "object",
"properties" : {
"message" : {"type" : "string"},
"who" : {"type" : "string"}
}

if i send "message" : "Hello" , "who":"bob" , "offender":12 , Flag Off = it says green , FlagOn = it says red
the topic beeing to spot that the server returns undocumented fields ...

[daveshanley]

I don't see why not. I would assume that the JSON schema lib we use would handle that, but if not, it's logic that can be added in to our lib.

[LasneF]

notice that redocly issue a warning for such use case and i think it is wise

[CompositeCoding]

Just spent a day bashing my head against my desk lol.

My expectations for Wiretap as a spec validator is that a new key from a response, that is not present in the spec, would at least be able to trigger a warning. Reading this comment thread, it appears this functionality is not built-in.

I can give it a try to build this in.

[daveshanley]

Shipped as --strict-mode / strictMode: true.

https://pb33f.io/wiretap/configuring/#strict-mode