supabase-js 2.0
kiwicopple opened this issue ยท 8 comments
What?
We're using this task to plan any breaking changes that we might want to add to supabase-js as part of our 2.0 release:
(Possible) Features
- Update Type Implementation (import definitions at the constructor level): #125
- Better treeshaking: #151
- storage 2.0: supabase/storage-js#6
- standard error responses: supabase/auth-js#405
undefinedinstead ofnullfor bottom type: #244return: minimalby default- Nested columns: supabase/supabase#535 (reply in thread)
- Default to
nullsFirst: true: supabase/postgrest-js#239
Timeline
- No fixed timeline
Re: the tree-shaking in #151, we'll be modularizing each Supabase components right? (i.e. rest, auth, etc.) Combining them into one class felt hacky to me, esp. for those with overlapping function names (e.g. from() can accept '*' in realtime-js but not postgrest-js).
This also makes it easier to implement in other languages with less flexible OO features, esp. once we tackle iOS/Android.
One more item: standardizing error response format supabase/supabase#12739 supabase/auth-js#405
must have in v2 for better TypeScript type definitions for queries, kudos to @bnjmnt4n :
supabase-client (alternative TypeScript-based)
Better integration (and examples) with react-native and expo's auth methods
https://docs.expo.dev/versions/latest/sdk/auth-session/
Better integration (and examples) with react-native and expo's auth methods
Hey! Sorry if this is not the right place to reach out - I am currently integrating Superbase (V2) with latest Expo and I am running into few gotchas. I would like to have a chat and help you improve the DX for that platform, potentially with some examples. What would be the most convenient way to chat? If Discord, you can find me at grabbou#4925.
I believe this should be a showStopper for v2
Using Custom JWT's is an important feature, I'd say, and right now it's not supported
#553