Default tag should contains all latest apiVersion swagger file

[ruowan]

No description provided.

[chgennar]

@ruowan - i have the MISSING_APIS_IN_DEFAULT_TAG error showing up in a PR.

In my particular case, it looks like a change in casing is causing a discrepancy between an earlier and new version of the same API path. Should this MISSING_APIS_IN_DEFAULT_TAG use a case insensitive comparison? Or possibly should it rely on the operation ids instead of the paths?

[ruowan]

Thanks for your feedback. This errors use case sensitive comparison for paths and normalize path by ignore parameter. Operation id is more flexible than path.

I think I need to update this rule to use case insensitive comparison.

Could you share the PR link?

[chgennar]

Thanks for your feedback. This errors use case sensitive comparison for paths and normalize path by ignore parameter. Operation id is more flexible than path.

I think I need to update this rule to use case insensitive comparison.

Could you share the PR link?

This is the check that is failing on my PR. I think it's caused by a change in casing between two spec versions.
https://github.com/Azure/azure-rest-api-specs/pull/17439/checks?check_run_id=5378743491

[mc3784]

Hi @ruowan
the avocado check on my pr is also failing with this error: MISSING_APIS_IN_DEFAULT_TAG

I am not able to understand how to fix it, and would really appreciate some help. Here the link to the PR:
https://github.com/Azure/azure-rest-api-specs-pr/pull/6412/checks?check_run_id=5412195265