hi all, we're getting a weird issue with pactflow. Pactflow is flagging up an issue with the OAS schema on the ui, saying the schema validation failed, but publishing that schema and running a can-i-deploy flags up no problems for the provider, any ideas how to debug/what the problem could be?

What's the error? A validation of the OAS or a comparison error? I tend to use editor.swagger.io to sanity check an OAS for basic errors

Unable to parse "oas": Swagger schema validation failed.

Just checking then, does publishing the oas file as a contract not check for schema validation?

That’s correct, we don’t validate the OAS itself on publication - I’d need to go back to confirm why that’s the case (I recall having the discussion). It wouldn’t validate during

can-i-deploy

because that process is all about checking the results of the testing, and not directly performing the checks itself

would be grand if you could double check why the schema validation is not done on publication but done in ui, as the contract comparison then (for can-i-deploy) would presumably fail for the consumers of that OAS schema, as it can't be validated and thus used for contract validation?

That’s correct, it would fail. I’ve added it to a review of the improvements we are looking to bring to the comparison engine in ~Q3

thanks Matt! we'll look into some external validator for now and keep an eye out on the board in q3 🙂