Single Fetch: TypeScript implementation of defineLoader doesn't support records with arrays about remix HOT 8 OPEN

@tomiwaajayi either stop using defineLoader or override it to support your requirements.

This function is there just to help with types. It's not a requirement.

from remix.

@tomiwaajayi we're currently looking into good options/tradeoffs

A temporary fix would be to rework your type in way to where it undoes it's definition as an interface. You can do this through type utilities or by rewriting the type

For example, if you have an interface like

interface BlogPost {
  title: string;
  authors: { name: string }[];
}

Pick<BlogPost, 'title' | 'authors'>

will get it to work.

That's not a perfect solution by any means, nor the officially recommended one, but remember that Single Fetch is still an unstable API, so right now any suggestions I have are going to be a hack around the final solution

from remix.

Here's a couple of implementations found in type-fest discussions:

> playground <

But beware, none of them happen to be exported from type-fest/index.d.ts at the moment. Don't know if by mistake or by design, because I found ConditionalSimplifyDeep in their source code.

from remix.

I have a similar issue.
I am using the unstable_defineLoader fn which is meant to improve type safety (according to the docs)

my loader returns this

return { store, cart, ENV: getEnv(), userPrefs: userPrefsCookie, transactionRef, }

And I get errors that saying cart is not of type Serializable

from remix.

I entered a little rabbit hole and all roads lead to this: microsoft/TypeScript#50087 (comment)

It seems like this is an intended mechanic in TS. Workaround would be to use type over interface, although that is not always possible (my original issue is caused by an interface imported from 3rd party package 😢).

More cases in the > playground <.

EDIT: I added more mixed cases, it seems like it has to be all type: > playground <

from remix.

Yep, I ran into this too, and @pcattori confirmed exactly what you said

Thanks for adding the types. Definitely a problem for 3rd party packages like you mentioned

from remix.

@brookslybrand
Is there any temp fix for this ?

Or we'd have to wait for some update from the remix team.

For context:
We have a types repo shared by backend team and frontend team.
So it's basically impossible for us to change all interfaces to type.

from remix.

Thanks @kiliman @brookslybrand @KubaJastrz

from remix.