Not currently, as we generate the entire thing from code examples and not annotations, so the format based parts of the contract are not representable.
You can enforce the contract in the code though to ensure adherence to the desired spec of length/format - use the Lens system to enforce it for headers and queries through map() calls
For body elements, you can write simple wrapper data class types to enforce the contract and add them as custom mappings into your Jackson config.
For.both of these you will at least get the safety of parsing the input correctly or blowing up with a 400.
07/11/2019, 3:22 PM
Hmm not sure if I follow, if there an example or a link to one?