Allow to set router's futures

[artaommahe]

Is your feature request related to a problem? Please describe.
Since version 6.28.0 react-router-dom spams a lot of warnings about enabling v7 futures in console. storybook-addon-remix-react-router provides no way so set them

Describe the solution you'd like
Add futures object to reactRouter storybook options and pass it to the react-router-dom.

Describe alternatives you've considered

-

Additional context
https://reactrouter.com/en/6.27.0/upgrading/future#update-to-latest-v6x
remix-run/react-router#12245

[JesusTheHun]

@artaommahe Can you try the canary version ?

npm i [email protected]

[artaommahe]

@JesusTheHun just checked - the change in this version covers only RouterProvider`s future field, but doesn't cover createBrowserRouter's future field, that has much more flags to be set to suppress those annoying warnings. Our current futures setup for the app to suppress all warnings looks like this

const router = createBrowserRouter([/* routes list */], {
    future: {
      v7_relativeSplatPath: true,
      v7_fetcherPersist: true,
      v7_normalizeFormMethod: true,
      v7_partialHydration: true,
      v7_skipActionErrorRevalidation: true,
    },
});

<RouterProvider
  router={router}
  future={{
    v7_startTransition: true,
  }}
/>

also the typings for the implemented RouterParameters.future are a bit wrong. If that field is used with a RouterProvider then the type should be the same as RouterProviderProps.future?: Partial<Pick<FutureConfig, "v7_startTransition">>; from the react-router

[JesusTheHun]

Hey @artaommahe 👋 can you give a try to the latest canary please ?

npm i [email protected]

[artaommahe]

@JesusTheHun now it works properly for futures passed to the createBrowserRouter, but doesn't support futures passed to the RouterProvider.future 😅 , like v7_startTransition. So most warnings are finally gone, except one related to v7_startTransition

[JesusTheHun]

@artaommahe Oh ok. They gave the same name to two different interfaces.
I've tried locally and it works just fine now :)

npm i [email protected]

[artaommahe]

@JesusTheHun we've already updated to v7 😅