Currently when the response mock engine generates a response using the MockGenerator, the generated responses contain only examples for individual properties that are marked as required, see tests for more details.
The reason why generated responses contain only examples for required properties is a side-effect of using mock generator for validation. While it makes sense for validating required fields for requests, it shouldn't affect the response generation.
Changes:
- By default, disables the required check on the response mock engine to ensure that all examples for individual properties are used in generated mock responses.
- Introduces a new configuration option,
enable-all-mock-response-fields, to allow only the use of required field examples in the generated mock responses when set tofalse.
This fix uses pb33f/libopenapi#295
Wiretap just blindly rewrites paths that match any configuration.
Some (poorly written) APIs don't necessarily want to rewrite everything under a specific resource location.
The current way to do this is to add a dummy path rewrite that takes precedence. This is kind of hacky and also doesn't jump over target rewriting.
