From 990ac999a3c6841926a820b3613f614656a537a9 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Tue, 26 Dec 2023 11:23:44 -0500
Subject: [PATCH] Bump react-router-dom-v5-compat from 6.20.0 to 6.21.1 (#2075)
Bumps
[react-router-dom-v5-compat](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom-v5-compat)
from 6.20.0 to 6.21.1.
Sourced from react-router-dom-v5-compat's
releases. ... (truncated) Sourced from react-router-dom-v5-compat's
changelog. Add a new This fix was originally added in #10983
and was later reverted in #11078
because it was determined that a large number of existing applications
were relying on the buggy behavior (see #11052) The Bug
The buggy behavior is that without this flag, the default behavior when
resolving relative paths is to ignore any splat
( The Background
This decision was originally made thinking that it would make the
concept of nested different sections of your apps in
Any paths like Release notes
react-router-dom-v5-compat@6.4.0-pre.15
Patch Changes
react-router-dom-v5-compat@6.4.0-pre.11
Patch Changes
react-router-dom-v5-compat@6.4.0-pre.10
Patch Changes
react-router-dom-v5-compat@6.4.0-pre.9
Patch Changes
react-router-dom-v5-compat@6.4.0-pre.8
Patch Changes
react-router-dom-v5-compat@6.4.0-pre.7
Patch Changes
react-router@6.4.0-pre.7
react-router-dom@6.4.0-pre.7
react-router-dom-v5-compat@6.4.0-pre.6
Patch Changes
react-router-dom
peer dependency version
react-router-dom-v5-compat@6.4.0-pre.5
Changelog
6.21.1
Patch Changes
react-router@6.21.1
react-router-dom@6.21.1
6.21.0
Minor Changes
future.v7_relativeSplatPath
flag to implement
a breaking bug fix to relative routing when inside a splat route. (#11087)*
) portion of the current route path.<Routes>
easier if relative routing would
replace the current splat:<BrowserRouter>
<Routes>
<Route path="/" element={<Home />} />
<Route path="dashboard/*" element={<Dashboard />}
/>
</Routes>
</BrowserRouter>
/dashboard
, /dashboard/team
,
/dashboard/projects
will match the Dashboard
route. The dashboard component itself can then render nested
<Routes>
:function Dashboard() {
return (
<div>
<h2>Dashboard</h2>
<nav>
<Link to="/">Dashboard Home</Link>
<Link to="team">Team</Link>
<Link to="projects">Projects</Link>
</nav>
<Routes>
<Route path="/" element={<DashboardHome
/>} />
<Route path="team"
element={<DashboardTeam />} />
<Route path="projects"
element={<DashboardProjects />} />
</Routes>
</div>
... (truncated)
08cda17
chore: Update version for release (#11132)e5d73cf
chore: Update version for release (pre) (#11131)cc4436c
Update changelogs for useResolvedSplat example69ba50e
chore: Update version for release (#11114)ea0ffee
chore: Update version for release (pre) (#11095)373b30c
chore: Update version for release (pre) (#11091)56b2944
chore: Update version for release (pre) (#11090)ee5fcd5
Generate release notesddc2b94
chore: Update version for release (pre) (#11089)149ad65
Add future.v7_relativeSplatPath flag (#11087)