From b1b7bbffb8cf7f4c18027d50f0dedd9da25fbcd5 Mon Sep 17 00:00:00 2001 From: loka shafeek <34503724+loka1@users.noreply.github.com> Date: Thu, 22 Feb 2024 18:58:41 +0200 Subject: [PATCH] docs: Update wildcard route component to PageNotFoundComponent (#54570) This PR enhances the Angular documentation by replacing the placeholder `` with the actual `PageNotFoundComponent` in the wildcard route configuration. This update ensures that the documentation accurately reflects the recommended practice for handling page-not-found scenarios. Additionally, it addresses the issue where HTML entities like `<` were being displayed instead of the desired `<` symbol, resulting in clearer and more readable documentation for users. PR Close #54570 --- aio/content/guide/router.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/router.md b/aio/content/guide/router.md index beeaf6f5892..86d629e1c75 100644 --- a/aio/content/guide/router.md +++ b/aio/content/guide/router.md @@ -184,7 +184,7 @@ The Angular router selects this route any time the requested URL doesn't match a To set up a wildcard route, add the following code to your `routes` definition. ``` -{ path: '**', component: <component-name> } +{ path: '**', component: PageNotFoundComponent } ``` The two asterisks, `**`, indicate to Angular that this `routes` definition is a wildcard route.