Mocking & Validate problems with imported OAS3

[savage-alex]

When using the validate option on an API when an OAS3 definition is included that contains referenced path parameters the validator always fails.

It cannot see that a path paramter exists in the schema that is referenced (it also appears to break the other items too) and causes a circular loop of fix the sync issues round and round.

API to import:
https://app.swaggerhub.com/apis/AdvancedComputerSoft/example-pet-inventory/1.0.5
Output from validate

Note importing a fully resolved version (you can export it from the link) causes no errors so I think its another problem with referenced parameters

[VShingala]

@savage-alex As we are currently we are not supporting remote references inside the definition, validator is not able to resolve required path parameters and flagging them as missing while validation.

And you are correct that this is breaking further flows. We will be taking a look at this. Meanwhile to make validation work properly, all references has to be local. We have a separate ticket for supporting remote refs here - #8827 and let you know any updates there.