From 9a6cb89b8da13266fd589b71a978677628099253 Mon Sep 17 00:00:00 2001 From: Joonas Westlin Date: Mon, 22 May 2017 22:23:48 +0300 Subject: [PATCH] Adjusted example error message to reflect the situation that causes the error. --- src/Microsoft.AspNetCore.Routing/Template/TemplateParser.cs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/Microsoft.AspNetCore.Routing/Template/TemplateParser.cs b/src/Microsoft.AspNetCore.Routing/Template/TemplateParser.cs index 4ef9e394de..a1fb6d5ceb 100644 --- a/src/Microsoft.AspNetCore.Routing/Template/TemplateParser.cs +++ b/src/Microsoft.AspNetCore.Routing/Template/TemplateParser.cs @@ -346,8 +346,8 @@ namespace Microsoft.AspNetCore.Routing.Template { // The optional parameter is preceded by something that is not a literal. // Example of error message: - // "In the segment '{RouteValue}-{param?}', the optional parameter 'param' is preceded - // by an invalid segment '-'. Only a period (.) can precede an optional parameter. + // "In the segment '{RouteValue}{param?}', the optional parameter 'param' is preceded + // by an invalid segment '{RouteValue}'. Only a period (.) can precede an optional parameter. context.Error = string.Format( Resources.TemplateRoute_OptionalParameterCanbBePrecededByPeriod, segment.DebuggerToString(),