[Task]: Reject conflicting routes for Rest API and other types
Open
@renuka-fernando is already working on this.
Since May 13, 2026.
Area/Gateway
Aspect/API
Type/Task
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
The existing behaviour accepts conflicting routes, which may leads to ambiguous behaviour in the runtime.
We allow, same context to be in the Rest API, but we should not allow conflicting routes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.