feat: storage api #136
feat: storage api #136
Conversation
|
after uploading avatar if you refresh the browser it will show related to this bug on gotrue-js supabase/auth-js#67 |
…s for "profile" data (public), and "user data" (private)
…to feat/storage-api
…to feat/storage-api
…to feat/storage-api
…uard against null sessions
example/next-storage/pages/index.tsx
Outdated
| setSession(session) | ||
| }) | ||
|
|
||
| realtimeProfiles = supabase |
There was a problem hiding this comment.
@phamhieu you had a problem with realtime only returning one item right? What code changes did you make to fix it? I want to make sure we're suggesting the best method for next.js/react
There was a problem hiding this comment.
I update the code to use useReducer. Then on realtime callback i use dispatch to trigger change on my UI. It works nicely
| file: File | ||
| ): Promise<{ data: { message: string } | null; error: Error | null }> { | ||
| try { | ||
| if (!isBrowser()) throw new Error('No browser detected.') |
There was a problem hiding this comment.
I'll have to check what other libs are doing here for the Node environment
|
🎉 This PR is included in version 1.7.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What kind of change does this PR introduce?
Implement storage api with a
next-storageexample app.What is the current behavior?
To run example app:
supabase-jsand checkoutfeat/storage-apibranchnpm run buildcd example/next-storage/.env.localfile undernext-storageappnpm run devWhat is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context