New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vendor specific content types are not providing correct cross comparison #12
Comments
Great work - thanks Yousaf! I'll add to our backlog for review and prioritisation. |
@mefellows awesome, do you know when this makes it into a next release? |
Just in case you meant "released to PactFlow", this will happen in the next few days, likely tomorrow. |
I've just tested the above on the latest version (12.1.0) and they all fail validation - which is expected. I think we can close this now? |
Sounds good Matt and yeah good shout on "released to PactFlow" We will report back here when this lands in PactFlow, but for now the thread will be closed. If anyone reading has any new issues, please feel free to fill out a new issue :) |
Pre-condition
Vendor specific extension
headers: { “Content-Type”: “application/vnd.api+json” }
Repro https://github.com/pactflow/swagger-mock-validator/tree/vnd_issue/issues/vnd
Expected behaviour.
All above cases should fail validation.
If consumer and provider specify vendor specification application/json types (and other content-types), they should support the same validation as per regular mime times
The text was updated successfully, but these errors were encountered: