To reproduce this bug, one can set the translation key and the route name for an Action route. If there are multiple cultures that the translation provider can translate to, there will be route name duplications.
With the current implementation of AttributeRouting, there is no way of using TranslationKeys and customized route names; because currently RouteSpecification does not have a property regarding the culture (language) that the routing belongs to. So using a custom RouteNameBuilder is not an option too.
To reproduce this bug, one can set the translation key and the route name for an
Actionroute. If there are multiple cultures that the translation provider can translate to, there will be route name duplications.With the current implementation of AttributeRouting, there is no way of using
TranslationKeys and customized route names; because currentlyRouteSpecificationdoes not have a property regarding the culture (language) that the routing belongs to. So using a customRouteNameBuilderis not an option too.