Cascade Created Duplicate API Endpoints
API has duplicate endpoints with the same path and method after Cascade generated new controller methods. This causes routing conflicts where requests hit the wrong handler, or Spring Boot fails to start due to ambiguous endpoint definitions.
Cascade generated endpoints without checking for existing implementations.
Error Messages You Might See
Common Causes
- Cascade added @GetMapping("/api/users") when it already exists in same controller
- Cascade added new controller with overlapping routes as existing controller
- Path parameter mismatches: /users/{id} and /users/{userId} treated as duplicates
- Cascade didn't check base @RequestMapping value on controller class
How to Fix It
Search codebase for duplicate @RequestMapping/@GetMapping/@PostMapping annotations. Verify each unique path is handled by only one method. Review Cascade's generated code and remove duplicate endpoints. Consolidate logic if both versions handle same functionality. Run './gradlew compileKotlin' to detect conflicts.
Real developers can help you.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
How do I find duplicate endpoints?
Use IDE search for @RequestMapping/@GetMapping/@PostMapping. Check both method names and full path (base + method path).
Can two endpoints have same method and path?
No, only one handler per HTTP method+path. Different path params (@PathVariable) create different routes.