Skip to content

Best practice to handle XMS_EXAMPLE_NOTFOUND_ERROR check to support Canonical swagger #1043

Open

Description

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
image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions