From 3f9f1fd648d6a45583c214601dd6b882e6c5091b Mon Sep 17 00:00:00 2001 From: wwenrr Date: Wed, 1 Apr 2026 11:40:22 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Clarify=20multi-method=20operati?= =?UTF-8?q?on=5Fid=20note=20in=20docs?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../docs/advanced/path-operation-advanced-configuration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/docs/advanced/path-operation-advanced-configuration.md b/docs/en/docs/advanced/path-operation-advanced-configuration.md index ffaf246fa7..79f34387bb 100644 --- a/docs/en/docs/advanced/path-operation-advanced-configuration.md +++ b/docs/en/docs/advanced/path-operation-advanced-configuration.md @@ -18,11 +18,11 @@ You would have to make sure that it is unique for each operation. If you register the same endpoint function for multiple HTTP methods with `api_route()` / `add_api_route(..., methods=[...])`, OpenAPI operation IDs can -conflict unless you set explicit unique `operation_id` values. +still conflict. If you need unique operation IDs in generated OpenAPI clients, prefer separate -path operation decorators (for example `@app.get()` and `@app.post()`) or set -an explicit `operation_id` per operation. +path operation decorators (for example `@app.get()` and `@app.post()`) so each +operation can define its own `operation_id`. ///