Update asp0022.md (#30969)
* Update asp0022.md * Update aspnetcore/diagnostics/asp0022.md Co-authored-by: Tom Dykstra <tdykstra@microsoft.com> --------- Co-authored-by: Tom Dykstra <tdykstra@microsoft.com>pull/30972/head
parent
a87574e638
commit
cc6a89debb
|
@ -4,7 +4,7 @@ description: "Learn about analysis rule ASP0022: Route conflict detected between
|
|||
author: tdykstra
|
||||
monikerRange: '>= aspnetcore-8.0'
|
||||
ms.author: tdykstra
|
||||
ms.date: 03/24/2023
|
||||
ms.date: 11/08/2023
|
||||
uid: diagnostics/asp0022
|
||||
---
|
||||
# ASP0022: Route conflict detected between route handlers
|
||||
|
@ -34,3 +34,9 @@ Do not suppress a warning from this rule.
|
|||
## Notes
|
||||
|
||||
[ASP0023](xref:diagnostics/asp0023) warns on route conflicts in ASP.NET Core MVC apps, this analyzer warns on route conflicts in [minimal API](xref:fundamentals/apis) apps.
|
||||
|
||||
This analyzer is intentionally conservative about duplicate routes it reports to avoid false positives:
|
||||
|
||||
* The analyzer only reports duplicate routes declared in the same code block in a method. Duplicate routes in different branches of an `if` statement aren't reported because the analyzer can't statically determine which will be used at runtime.
|
||||
* The analyzer only reports duplicate routes with known metadata. Unknown methods called on a route handler might add new metadata that is then used to customize how the route is matched.
|
||||
|
||||
|
|
Loading…
Reference in New Issue