Concise shorthand for defining a typed path template.
When multiple registered templates validate the same URL, the server ranks
them by specificity: exact static routes first, then routes with more
literal path segments, then routes with fewer dynamic segments.
Registration order breaks ties between equally specific routes. This
precedence applies to both HTTP endpoints and WebSocket subscriptions.
Concise shorthand for defining a typed path template.
When multiple registered templates validate the same URL, the server ranks them by specificity: exact static routes first, then routes with more literal path segments, then routes with fewer dynamic segments. Registration order breaks ties between equally specific routes. This precedence applies to both HTTP endpoints and WebSocket subscriptions.
Example: With parameters
Example: Static path (no parameters)
Param: propsOrStrings
Either a property map for typed path segments, or a
TemplateStringsArraywhen used directly as a tagged template.Returns
A
ParseStringSchemaBuilder, or a tagged-template function that produces one.