Is ClientDataFunctionArgs context typing incorrect?

[andrewjroberts]

Hey @ mainly maintainers,

I was trying to unit test my route clientLoaders, e.g.

await clientLoader({ request: fakeRequest, params: {}, context: {} })

And I noticed the context type is required, even though the comment above the property says it should be undefined if the future.unstable_middlewareis not enabled:

    /**
     * When `future.unstable_middleware` is not enabled, this is undefined.  
     *
     * When `future.unstable_middleware` is enabled, this is an instance of
     * `unstable_RouterContextProvider` and can be used to access context values
     * from your route middlewares.  You may pass in initial context values in your
     * `<HydratedRouter unstable_getContext>` prop
     */
    context: unstable_RouterContextProvider; 

In the ServerDataFunctionArgs, it's conditional on MiddlewareEnabled:

    context: MiddlewareEnabled extends true ? unstable_RouterContextProvider : AppLoadContext;   

I know @brophdawg11 you just landed a PR for the createRoutesStub types, is this related to the ongoing issues faced?

react-router/packages/react-router/lib/types/route-module-annotations.ts

Line 70 in c06ec85

type ClientDataFunctionArgs<T extends RouteInfo> = {