React Router 7: Warning about missing trailing "*" in parent route despite following documentation - how to handle nested routes correctly?

[s-matthies]

I updated my application from React Router v6 to v7 and after adjusting my routes according to the documentation, I encountered a warning about a missing trailing "*". However, my routing works as expected.
(I followed the React Router v7 Upgrade Guide for handling nested routes.)

Setup

• React Router version: 7.4.1
• React version: 19.0.0

Current Implementation

Following the v7 documentation for nested routes, I changed from:

<Route path="projects/*" element={<Projects />} />

to:

<Route path="projects">
  <Route path="*" element={<Projects />} />
</Route>

The Projects component has its own internal routes and navigation:

// Projects.tsx
export function Projects(): React.JSX.Element {
    const parentPath = useResolvedPath('').pathname;

    return (
        <>
            <ProjectsSubnavigation />
            <Routes>
                <Route index element={<ProjectsOverview onlyProjects={true} onlyGrid={true} />} />
                <Route path="rejections" element={<ProjectsRejections />} />
                <Route path="list" element={<ProjectsList />} />
                <Route path=":projectArg" element={<ProjectsForm parentPath={parentPath} />} />
            </Routes>
        </>
    );
}

// ProjectsSubnavigation.tsx
export function ProjectsSubnavigation(): React.JSX.Element {
    return (
        <Subnavigation
            items={[
                { label: 'Übersicht', to: '' },
                { label: 'Absagen', to: 'rejections' },
                { label: 'Detailliste', to: 'list' },
            ]}
        />
    );
}

Current Behavior

• The navigation works correctly (can navigate to /projects, /projects/rejections, /projects/list, etc.)
• But I get this warning:

Warning:
You rendered descendant <Routes> (or called 'useRoutes()') at "/projects" (under <Route path="projects">) but the parent route path has no trailing "*". This means if you navigate deeper, the parent won't match anymore and therefore the child routes will never render.

My Question:

• Is there something I might have missed in the route setup that could be causing this warning?
• How can I resolve this warning without breaking the routing behavior?