Francois LASNE
Francois LASNE
given the illustration there https://json-schema.org/understanding-json-schema/reference/enum it would be good to add a precision that the enum validation, for string, is case sensitive , and so introducing in the sample list...
**Problem description ** As i am handling lots of issues in an api spec , i would like that the report is pushed on a file. On windows (at least)...
**Describe the bug** given an API specification mixing required keyword and readOnly , writeOnly redocly generate a warning wheras it should not **To Reproduce** given the minimal files attached [small.json](https://github.com/Redocly/redocly-cli/files/14097153/small.json)...
**Describe the bug** no-invalid-media-type-example is behaving incorrectly and raising a false positive error when using XML OAS specify dedicated tag to handle XML around tag names rewrite , name space,...
Documentation would requires more details for instance i got  1st lines indicate leak found ; yes but what can of leak ? , still the test passed successfully 2nd...
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...
current behaviour when there is a validation error is that it returns a 502 the enhancement i propose is that the returned payload contains a structured error containning this list...
Given Wiretap as a proxy , Given that there is HTTP rewritting it would be nice to have better logging on the rewrite applied here i got in wiretap logs...
When setting WireTap as a validation proxy , it would be nice to return as well the error details to the client and not only the 502 could be returning...
given this object , vaccum raise an error about pom not defined .\component-descriptor.yml:2617:7 | error | `required` field `pom ` is not defined in `properties` | oas-schema-check accoding to JSonSchema...