Ian Ownbey

@cpojer Often people like to have assets live alongside the javascript, and when you have a project broken up into yarn workspaces that can mean that assets live above the...

I believe the asset is always referenced from the projectRoot and not from watchFolders, although would be interested in understanding how I could fix this with watchFolders https://github.com/facebook/metro/blob/6f8b7b8357ec8e5b2ac35cecb99cef7417134374/packages/metro/src/Assets.js#L277

Maybe to better illustrate in our project we have multiple yarn workspaces, one for a design system `packages/designSystem/src/` and one for the app `packages/app/[src, ios, android, etc]`. We need to...

Happy to look into that. Do you think the hash or moving the path to a param would be easier? @cpojer I’d think it’d be better to request all assets...

Ah nice catch @belemaire. Updated test and added that. It might be good to only replace ..'s at the start of the path, happy to do that if people would...

LG. Maybe remove whitefix changes

I believe this has been fixed, you need to use a db-url to generate the types locally for now https://github.com/supabase/postgrest-js/pull/426

Oh woops! My bad

This is actually a pretty gnarly issue because postgrest returns the child object not wrapped in an array but typescript now thinks it is in an array. This makes runtime...

I am seeing the return types be correct as the #223 states, but the typescript types are still totally ambiguous between array or single response which makes the return types...