✳flâneur — a map of the web's best reading

[supabase-js v2] Improve Types Implementation for Nested Queries · Issue #303 · supabase/postgrest-js

github.com · 703 words · saved by 1 readers

Hi there, I tried implementing supabase-js v2, and first was happy to see the type generation out of select queries. But the real issues I have are still not solved with the new approach, these are nested tables types. So let's imagine you have this data structure id, title, actors(name, birth_date), typescript will catch the id and title, of the movie, but not the name and birth_date of the nested relation. If I am now going to add this info manually like this: there will be a lot of redunancy in the implementation. Since we have to define the table cols twice. Of course it would be perfect if nested relations would work out of the box. I see that this would be very difficult to do, and that's maybe why you didn't. I would essentially suggest to export this type, to create something like this: I peeked into the type definitions of the new supabase-js v2 library, and saw a GetResult type coming from @supabase/postgrest-js/dist/module/select-query-parser. I have implemented something wi

[supabase-js v2] Improve Types Implementation for Nested Queries · Issue #303 · supabase/postgrest-js · GitHub Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} Uh oh! There was an error while loading. Please reload this page . This repository was archived by the owner on Jan 23, 2026. It is now read-only. supabase / postgrest-js Public archive Uh oh! There was an error while

Explore this link on the map →

related reading