Browse Source
When a route is added with multiple HTTP methods (e.g., methods=["POST", "DELETE"]), all methods were getting the same auto-generated operationId based only on the first method, causing "Duplicate Operation ID" warnings. The fix appends the method name to the operationId when: 1. No explicit operation_id is provided 2. The route has multiple methods This ensures unique operationIds for each method while maintaining backward compatibility for single-method routes and explicit operation_id usage. Fixes #13175pull/14827/head
1 changed files with 4 additions and 0 deletions
Loading…
Reference in new issue