docs(router): usage of routeFilePrefix for file-based routing (#4845)

Author: leesb971204

docs/router/api/file-based-routing.md

@@ -13,6 +13,7 @@ The following options are available for configuring the file-based routing:
 - [`virtualRouteConfig`](#virtualrouteconfig)
 - [`routeFilePrefix`](#routefileprefix)
 - [`routeFileIgnorePrefix`](#routefileignoreprefix)
+- [`routeFileIgnorePattern`](#routefileignorepattern)
 - [`indexToken`](#indextoken)
 - [`routeToken`](#routetoken)
 - [`quoteStyle`](#quotestyle)
@@ -58,6 +59,12 @@ This option is used to configure the Virtual File Routes feature. See the "Virtu
 
 By default, this value is set to `undefined`.
 
+### `routeFilePrefix`
+
+This option is used to identify route files in the route directory. This means that only files that start with this prefix will be considered for routing.
+
+By default, this value is set to `` and as such all files in the route directory will be considered for routing.
+
 ### `routeFileIgnorePrefix`
 
 This option is used to ignore specific files and directories in the route directory. This can be useful if you want to "opt-in" certain files or directories that you do not want to be considered for routing.
@@ -81,12 +88,6 @@ This option is used to ignore specific files and directories in the route direct
 
 By default, this value is set to `undefined`.
 
-### `routeFilePrefix`
-
-This option is used to identify route files in the route directory. This means that only files that start with this prefix will be considered for routing.
-
-By default, this value is set to `` and as such all files in the route directory will be considered for routing.
-
 ### `routeToken`
 
 As mentioned in the Routing Concepts guide, a layout route is rendered at the specified path, and the child routes are rendered within the layout route. The `routeToken` is used to identify the layout route file in the route directory.