This repository was archived by the owner on Dec 14, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
MapAreaRoute override existing area constraint #4847
Labels
Milestone
Comments
@Eilon This is in up-for-grabs.. I can do it ? |
I'm not @Eilon - but yes!
|
ok Thanks :) |
Yup, go for it! |
@ajaybhargavb assigning this to you to track @iscifoni 's PR at #4954. |
ajaybhargavb
pushed a commit
that referenced
this issue
Jul 11, 2016
* #4847 Fix MapAreaRoute override existing area constraint Modify Test project Modify web test routing * wrong field tested * IntRouteConstraint expected * Default for area route on Travel area * Removed commented code simplify constraintsDictionary area assign renamed test method * test name * renamedd test to MapAreaRoute_DoesNotReplaceValuesForAreaIfAlreadyPresentInConstraintsOrDefaults
Thanks! @iscifoni |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
When using
MapAreaRoute
with an existing set of constraints containing thearea
entry, the entry will be overriden by the area name passed as a parameter. I would expect it to be kept in this case.For example, I want to pass an explicit constraint object for
area
instead of a string to prevent Regex comparisons on this route.The text was updated successfully, but these errors were encountered: