Azure / Azure/typespec-azure

TypeSpec Normalization Tracking

Open
#5,005 0 comments 0 reactions 1 assignee Claimed by @markcowl View on GitHub
epic needs-area
Dominant language
TypeScript
Stars
27
Forks
90
Avg merge
1d 22h
Merged PRs (30d)
156

Description

## Support Work
- [ ] Skill for making api-neutral changes to PRs
- [ ] Determine criteria and identification tool for high-pri specs (importance, last updated)

## P1 Issues (Impacting SDKs or CLI)
- [ ] Network Spec
- [x] Decide on and fix VMSS API issue
- [x] Agree on and Fix Suppression Issue (private decorators, featureFiles)
- [ ] Document this pattern in our conversion advice
- [x] Set typespec-autorest options
- [x] Specs that add the namespace to the schema name for types in generated OpenAPI (@pshao25 )
- [x] Identify specs that have this issue (public)
- [x] Identify specs that have this issue (private)
- [ ] Prioritize and fix high-pri specs
- [ ] Create a specs PR applying the change
- [ ] Validate no SDK breaking changes
- [x] Specs that incorrectly model LROs (wrong finalResult)
- [ ] Merge Linting rule
- [x] Identify specs form linting rule (public)
- [x] Identify specs from linting rule (private)
- [ ] Prioritize and fix high-pri specs
- [ ] Create a specs PR applying the change
- [ ] Validate no SDK breaking changes
- [x] Specs that use OpenAPI Decorators for important extensions:
- [x] Refine OpenAPI linting rule
- [x] Bar use of client-altering extensions [#3066](https://github.com/Azure/typespec-azure/issues/3066)
- x-ms-skip-url-encoding
- x-ms-enum
- x-ms-parameter-grouping
- x-ms-parameter-location
- x-ms-client-name
- x-ms-discriminator-value
- x-ms-client-flatten
- x-ms-parameterized-host
- x-ms-pageable
- x-ms-long-running-operation
- x-ms-long-running-operation-options
- x-nullable
- x-ms-internal
- x-ms-azure-resource
- x-ms-arm-id-details
- x-ms-secret
- [x] Identify specs from linting rule (public)
- [x] Identify specs from linting rule (private)
- [ ] Prioritize and fix high-pri specs
- [x] Specs that omit resource or resource operation decorators
- [x] Check in current linting pr
- [ ] Identify specs form linting rule (public)
- [ ] Identify specs from linting rule (private)
- [ ] Prioritize and fix high-pri specs
- [ ] Move Sql to use @featureFiles
- [ ] Deprecate @feature & associated decorators
- [ ] Remove @feature & associated decorators


## P2 Issues (Important Issues that don't break sdk/cli)
- [ ] Specs in the RPSaaSMaster exclusion list
- [ ] Specs that use implicitOptionality for PATCH requests
- [ ] Specs that use private decorators [#1333](https://github.com/Azure/typespec-azure/issues/1333)
- [ ] Specs that use string in place of Uri or arm-id
- [ ] Specs that unnecessarily use legacy operations
- [ ] Specs that use custom PrivateLinks, PrivateEndpointConnections, NSPs
- [ ] Specs that use custom resource-types
- [ ] Specs that use $ref siblings (esp. readOnly)
- [ ] Emission of readOnly + required (readOnly should make a property optional in swagger)
- [ ] Update ResourceNameParameter template to flag unnecessary property specification [#3017](https://github.com/Azure/typespec-azure/issues/3017)

## P3 Issues
- [ ] Specs that violate the `@doc` rule
- [ ] Specs that privately define ServiceGroups (ARM is working on this)
- [ ] Simple mechanism to change the response type name for a templated operation

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.