react-router 6.21.0-pre.0 → 6.21.0-pre.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,12 +1,18 @@
1
1
  # `react-router`
2
2
 
3
+ ## 6.21.0-pre.1
4
+
5
+ ### Patch Changes
6
+
7
+ - [REMOVE] Fix plumbing of future flags ([`558d7936`](https://github.com/remix-run/react-router/commit/558d7936cc8fe643374a2c9a9fdcf022e8c4c939))
8
+
3
9
  ## 6.21.0-pre.0
4
10
 
5
11
  ### Minor Changes
6
12
 
7
- - Add a new `future.v7_relativeSplatPath` flag to implenent a breaking bug fix to relative routing when inside a splat route. ([#11087](https://github.com/remix-run/react-router/pull/11087))
13
+ - Add a new `future.v7_relativeSplatPath` flag to implement a breaking bug fix to relative routing when inside a splat route. ([#11087](https://github.com/remix-run/react-router/pull/11087))
8
14
 
9
- This fix was originally added in [#10983](https://github.com/remix-run/react-router/issues/10983) and was later reverted in [#11078](https://github.com/remix-run/react-router/issues/110788) because it was determined that a large number of existing applications were relying on the buggy behavior (see [#11052](https://github.com/remix-run/react-router/issues/11052))
15
+ This fix was originally added in [#10983](https://github.com/remix-run/react-router/issues/10983) and was later reverted in [#11078](https://github.com/remix-run/react-router/pull/11078) because it was determined that a large number of existing applications were relying on the buggy behavior (see [#11052](https://github.com/remix-run/react-router/issues/11052))
10
16
 
11
17
  **The Bug**
12
18
  The buggy behavior is that without this flag, the default behavior when resolving relative paths is to _ignore_ any splat (`*`) portion of the current route path.
@@ -50,7 +56,7 @@
50
56
 
51
57
  **The Problem**
52
58
 
53
- The problem is that this concept of ignoring part of a pth breaks a lot of other assumptions in React Router - namely that `"."` always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using `"."`:
59
+ The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that `"."` always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using `"."`:
54
60
 
55
61
  ```jsx
56
62
  // If we are on URL /dashboard/team, and we want to link to /dashboard/team:
package/dist/index.js CHANGED
@@ -1,5 +1,5 @@
1
1
  /**
2
- * React Router v6.21.0-pre.0
2
+ * React Router v6.21.0-pre.1
3
3
  *
4
4
  * Copyright (c) Remix Software Inc.
5
5
  *
@@ -965,10 +965,7 @@ function RouterProvider(_ref) {
965
965
  router,
966
966
  navigator,
967
967
  static: false,
968
- basename,
969
- future: {
970
- v7_relativeSplatPath: router.future.v7_relativeSplatPath
971
- }
968
+ basename
972
969
  }), [router, navigator, basename]);
973
970
 
974
971
  // The fragment and {null} here are important! We need them to keep React 18's
@@ -985,7 +982,10 @@ function RouterProvider(_ref) {
985
982
  basename: basename,
986
983
  location: state.location,
987
984
  navigationType: state.historyAction,
988
- navigator: navigator
985
+ navigator: navigator,
986
+ future: {
987
+ v7_relativeSplatPath: router.future.v7_relativeSplatPath
988
+ }
989
989
  }, state.initialized ? /*#__PURE__*/React.createElement(DataRoutes, {
990
990
  routes: router.routes,
991
991
  future: router.future,