Inline constraints

This one contains all the remaining constraints except the Regex constraint which is not registered to work as inline constraint. I will add it as a separate commit/PR, it needs special handling as it depends on the behavior of not splitting the parameters on a comma. ( The code we had would not work as today we have two constructors for RegexConstraint)..More on this in the PR.
Your lunk

-----Original Message-----
From: "Harsh Gupta" <notifications@github.com>
Sent: ‎6/‎16/‎2014 3:42 PM
To: "aspnet/Routing" <Routing@noreply.github.com>
Cc: "Yishai Galatzer" <yishai_galatzer@yahoo.com>
Subject: Re: [Routing] Inline constraints (#67)

In test/Microsoft.AspNet.Routing.Tests/RouteConstraintsTests.cs:
> +        [InlineData("not-parseable-as-date", false)]
> +        [InlineData(false, false)]
> +        public void DateTimeRouteConstraint(object parameterValue, bool expected)
> +        {
> +            // Arrange
> +            var constraint = new DateTimeRouteConstraint();
> +
> +            // Act
> +            var actual = TestValue(constraint, parameterValue);
> +
> +            // Assert
> +            Assert.Equal(expected, actual);
> +        }
> +
> +        [Theory]
> +        [InlineData("true", true)]
Can you point me to the link which says this? This is not specific to inline constraints, the case that you pointed out has to be dealt with while parsing the incoming values, and that's template matcher. BTW this is a good test to have. 
—
Reply to this email directly or view it on GitHub.