Skip to content

Normalize IP, DB, OS, IPv4, and IPv6 names in the management generator #61942

Description

@weikanglim

Parent: #61941

Add boundary-aware final-name normalization in Azure.Generator.Management for:

  • Ip -> IP
  • Db -> DB
  • Os -> OS
  • Ipv4 and IpV4 -> IPv4
  • Ipv6 and IpV6 -> IPv6

Apply it to model, extensible-enum/union type, enum type, and model-property providers. Replace repeated occurrences and preserve longer words such as Oslo, Ipsum, Osmosis, and dbz. Keep explicit IPV4/IPV6 spellings unchanged for compatibility.

Acceptance criteria

  • Normalization runs on the final provider name after existing structural transforms.
  • Positive, repeated, already-canonical, negative-boundary, and interaction tests pass.
  • Enum values, clients, operations, and parameters are excluded from this task.
  • No generated SDK source or API specification files are modified.

Measured potential cleanup: 945 C# decorators occupying 3,181 physical client.tsp lines.

Metadata

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.CodeGenIssues that relate to code generation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions