We have introduced canonical swagger for Multi-Versioning in Azure Process (Canonical Version) . Basically, the canonical swagger file is a union of versioned swaggers.
Here is an example of the canonical swagger in RPSaaSDev branch https://github.com/Azure/azure-rest-api-specs-pr/tree/RPSaaSDev/specification/dinwadevtest/resource-manager/Microsoft.Contoso
When we created a PR for RPSaaSMaster branch, it failed with XMS_EXAMPLE_NOTFOUND_ERROR. We can suppress the error, but want to check what would be the best practice in this case? Can we disable this XMS_EXAMPLE_NOTFOUND_ERROR check when it is for canonical swagger? Thanks.
We have introduced canonical swagger for Multi-Versioning in Azure Process (Canonical Version) . Basically, the canonical swagger file is a union of versioned swaggers.
Here is an example of the canonical swagger in RPSaaSDev branch https://github.com/Azure/azure-rest-api-specs-pr/tree/RPSaaSDev/specification/dinwadevtest/resource-manager/Microsoft.Contoso
When we created a PR for RPSaaSMaster branch, it failed with XMS_EXAMPLE_NOTFOUND_ERROR. We can suppress the error, but want to check what would be the best practice in this case? Can we disable this XMS_EXAMPLE_NOTFOUND_ERROR check when it is for canonical swagger? Thanks.