How deeply does ASP.NET Core in Action, 3e cover route constraint?

Explains parameter syntax, built-in types, combinations, optional values, matching behavior, and validation limits.

Route constraint

As explained in ASP.NET Core in Action, 3e

A route constraint is a rule attached to a route parameter that determines whether a URL value satisfies the requirements for matching a route template.

A route constraint is a rule attached to a route parameter. It narrows which URL values can match a route template, helping ASP.NET Core choose the correct endpoint before the handler runs. section 6.3.3

Constrain an integer parameter

Use a colon after the parameter name: app.MapGet("/fruit/{id:int}", (int id) => "Hello world!"). The route matches integer values such as 123, but not noninteger values. Without the constraint, a noninteger URL value can cause an exception when it is bound to the integer parameter. section 6.3.3

Common constraints include:

int, guid, and decimal require values convertible to those types. section 6.3.3
min(value) requires an integer at least the specified value, while length(value) requires a string of the specified length. section 6.3.3
Combine constraints with colons, and append ? when the constrained parameter is optional, such as {qty:int:max(10)?}. section 6.3.3

Table 6.2 A few route constraints and their behavior when applied (view table figure)

Constraint	Example	Description	Match examples
`int`	`{qty:int}`	Matches any `integer`	`123,` `-123,` `0`
`Guid`	`{id:guid}`	Matches any `Guid`	`d071b70c-a812-4b54-87d2-7769528e2814`
`decimal`	`{cost:decimal}`	Matches any `decimal` value	`29.99,` `52,` `-1.01`
`min(value)`	`{age:min(18)}`	Matches `integer` values of 18 or greater	`18,` `20`
`length(value)`	`{name:length(6)}`	Matches `string` values with a length of `6`	`Andrew,123456`
`optional` `int`	`{qty:int?}`	Optionally matches any integer	`123,` `-123,` `0,` `null`
`optional` `int` `max(value)`	`{qty:int:max(10)?}`	Optionally matches any integer of 10 or less	`3,` `-123,` `0,` `null`

Compare constraint syntax, accepted values, and matching examples in a compact reference table. section 6.3.3

Routing checks every constraint when matching a URL. If any constraint fails, the route is not a match and its endpoint is not executed. Use constraints for strict URL requirements or to distinguish similar routes, not for general input validation: invalid input can otherwise appear as a confusing 404 response. Built-in constraints also assume invariant culture. section 6.3.3 section 6.5

How ASP.NET Core in Action, 3e covers it

liveBook manning.com

Read ASP.NET Core in Action, 3e on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Pro ASP.NET Core 7, Tenth EditionA route constraint is a rule attached to a route parameter that restricts matching to values satisfying a specified condition.

Compare how 2 books explain route constraint →

Related concepts

validationcontrasts with · The process of checking data, behavior, systems, models, or results against defined criteria to assess their correctness, suitability, or acceptability.
route parameterconfigures · A route parameter is a named variable embedded in a URL path whose value is captured from a matching request to identify or select a resource or operation.
routingconfigures · Routing is the selection of a path, destination, or processing component to direct an item, request, or flow toward an intended endpoint.
routing middlewareuses · Routing middleware is an ASP.NET Core request-pipeline component that matches incoming requests to endpoints and stores the selected endpoint for subsequent processing.
overlapping route templateaddresses · An overlapping route template is a route template whose matching rules also match one or more other route templates for at least one URL.

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.