From b6f48dbe19eac8bce7b33e15e334fb2fd6739e67 Mon Sep 17 00:00:00 2001 From: Judy Bogart Date: Tue, 2 Apr 2019 11:01:48 -0700 Subject: [PATCH] docs: correct route path description (#29669) PR Close #29669 --- packages/router/src/config.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/packages/router/src/config.ts b/packages/router/src/config.ts index 6d624b94c9..cc0be4687c 100644 --- a/packages/router/src/config.ts +++ b/packages/router/src/config.ts @@ -363,7 +363,7 @@ export type RunGuardsAndResolvers = 'pathParamsChange' | 'pathParamsOrQueryParam export interface Route { /** * The path to match against, a URL string that uses router matching notation. - * Can include wild-card characters (*). [where is that defined?] + * Can be a wild card (`**`) that matches any URL (see Usage Notes below). * Default is "/" (the root path). */ path?: string; @@ -374,6 +374,7 @@ export interface Route { * By default, the router checks URL elements from the left to see if the URL * matches a given path, and stops when there is a match. For example, * '/team/11/user' matches 'team/:id'. + * * The path-match strategy 'full' matches against the entire URL. * It is important to do this when redirecting empty-path routes. * Otherwise, because an empty path is a prefix of any URL,