From c445bd67ccb65c022120c9aa81661bc5e304a056 Mon Sep 17 00:00:00 2001 From: Remix Run Bot Date: Thu, 24 Aug 2023 21:36:56 +0000 Subject: [PATCH] chore: format --- docs/discussion/02-routes.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/discussion/02-routes.md b/docs/discussion/02-routes.md index 9974c39927c..9556a16d974 100644 --- a/docs/discussion/02-routes.md +++ b/docs/discussion/02-routes.md @@ -85,7 +85,7 @@ app/ └── sponsored.tsx ``` -You can read more about the specific patterns in the file names and other features in the [Route File Conventions](../file-conventions/routes) reference. +You can read more about the specific patterns in the file names and other features in the [Route File Conventions][route-file-conventions] reference. Only the folders directly beneath `routes/` will be registered as a route. Deeply nested folders are ignored. The file at `routes/about/header/route.tsx` will not create a route. @@ -140,3 +140,5 @@ export default { ``` Remix's route configuration approach blends convention with flexibility. You can use the `routes` folder for an easy, organized way to set up your routes. If you want more control, dislike the file names, or have unique needs, there's `remix.config`. It is expected that many apps forgo the routes folder convention in favor of `remix.config`. + +[route-file-conventions]: ../file-conventions/routes