Resource action for the route the even count of segment
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 90
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 156
Description
We encountered this many times. For example, this [route](https://github.com/Azure/azure-rest-api-specs/blob/d6da37c3f230556d5edefd5cefccaeb9ecceaba3/specification/confluent/resource-manager/Microsoft.Confluent/stable/2024-07-01/confluent.json#L1621) belongs to the resource [`Organization`](https://github.com/Azure/azure-rest-api-specs/blob/d6da37c3f230556d5edefd5cefccaeb9ecceaba3/specification/confluent/resource-manager/Microsoft.Confluent/stable/2024-07-01/confluent.json#L254). However, the segments for this operation have even number. I know this might be anti-pattern. However, there are a lot of cases. I think we should design some template for this case.
Contributor guide
Research direction
Start by inspecting the linked confluent.json route and the Organization definition to understand the even-segment case. Read the existing issue discussion before proposing a template; done means an agreed design that supports these resource actions without breaking existing route conventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100