Azure / Azure/azure-rest-api-specs

Enums entries missing extension `x-ms-enum`

Open
#13,382 7 comments 0 reactions 0 assignees View on GitHub
Container Service Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

We have some swaggers that are missing `x-ms-enum` extension. For instance, this: https://github.com/Azure/azure-rest-api-specs/blob/ff541d84da3e56318de42e92222e9501a9ccb632/specification/compute/resource-manager/Microsoft.ContainerService/stable/2017-01-31/containerService.json#L359
In code generation, a code-name with number will be given to this enum type (for instance `Enum47`), and during the update of the swaggers, this code-name might change and cause unnecessary breaking changes.

Related issue: https://github.com/Azure/autorest.go/issues/571

Contributor guide

Open the contributing guide

Research direction

Start by inspecting specification/compute/resource-manager/Microsoft.ContainerService/stable/2017-01-31/containerService.json around line 359 and compare the enum declaration with the requested x-ms-enum extension. Search the Swagger specifications for other enum entries with the same omission, then verify that code generation no longer assigns unstable numeric names such as Enum47.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.