Azure / Azure/azure-rest-api-specs
Incorrect definition of "ScopeParameter" in resources client
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
Example:
https://github.com/Azure/azure-rest-api-specs/blob/34fcbc36b9974a9a4c28286883d464faecd3d70c/specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json#L5815-L5822
scope parameters MUST use the x-ms-skip-url-encoding autorest extention, otherwise this leads to issue like this:
https://github.com/Azure/autorest.python/issues/596
Example of correct definition:
https://github.com/Azure/azure-rest-api-specs/blob/34fcbc36b9974a9a4c28286883d464faecd3d70c/specification/authorization/resource-manager/Microsoft.Authorization/stable/2015-07-01/authorization-RoleAssignmentsCalls.json#L171-L178
Contributor guide
Research direction
Open specification/resources/resource-manager/Microsoft.Resources/stable/2019-10-01/resources.json around lines 5815-5822 and compare the ScopeParameter definition with the authorization RoleAssignmentsCalls.json example around lines 171-178. Confirm that the scope parameter uses the x-ms-skip-url-encoding extension, then verify the specification change addresses the linked AutoRest Python issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100