Azure / Azure/azure-rest-api-specs
Redis.CheckNameAvailability pattern is not implemented correctly
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
Current latest spec describes return type of an operation `checkNameAvailability` as void.
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/redis/resource-manager/Microsoft.Cache/stable/2018-03-01/redis.json#L91
In the generated code the method will be as `void checkNameAvailability(parameters)` and if it will not throw an exception (C#/Java) then the name is available.
Contributor guide
Research direction
Start with specification/redis/resource-manager/Microsoft.Cache/stable/2018-03-01/redis.json at the checkNameAvailability operation and review its declared response. Compare that definition with the generated C# and Java method behavior described in the issue; done means the specification and generated operation follow the intended name-availability pattern.
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
- 35/100