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
{{ message }}
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
In the event that you want to decide to treat route values as culture-sensitive, you have to duplicate a lot of code. Our other IValueProvider implementations accept a CultureInfo in the constructor.
See my answer here, route values are an outlier with respect to this question.
The text was updated successfully, but these errors were encountered:
Added a constructor with culture info. I wasn't sure if you wanted to add CultureInfo to the existing constructor. With the new constructor, I didn't need to modify several test classes such as DefaultModelBindingContextTest, RouteValueProviderTest and TestValueProvider.
Do you prefer a single constructor with the addition of CultureInfo, which includes updating the associated tests and factory?
In the event that you want to decide to treat route values as culture-sensitive, you have to duplicate a lot of code. Our other
IValueProvider
implementations accept aCultureInfo
in the constructor.See my answer here, route values are an outlier with respect to this question.
The text was updated successfully, but these errors were encountered: