You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
TranslationKey
s and customized route names; because currentlyRouteSpecification
does not have a property regarding the culture (language) that the routing belongs to. So using a customRouteNameBuilder
is not an option too.The text was updated successfully, but these errors were encountered: