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
Not sure how the builder is constructed right now, but I'd assume the filter op could go before or after the on handlers. Albeit, I don't know if all the filters are supported for Realtime as they are for the Data API, but all the more reason to statically constrain them?
This would be more along the lines of Firebase's Firestore syntax. Has there been any discussion on returning the entire data set? (aka the 'snapshots()' functionality? This would be huge, and I think it'd basically involve the library doing the logic that we'll be doing over and over on the client-side to keep the state of the data set (I'm sure it's more complex than that 🙃 ), and might help down the road for adding Offline functionality? I'd love to use the client as my state management as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm curious if the DX for realtime can be the same as it is for the regular API. I would imagine the filter string could just be built internally.
For example, from the docs:
Why not keep it consistent with the API, as something like:
Not sure how the builder is constructed right now, but I'd assume the filter op could go before or after the on handlers. Albeit, I don't know if all the filters are supported for Realtime as they are for the Data API, but all the more reason to statically constrain them?
This would be more along the lines of Firebase's Firestore syntax. Has there been any discussion on returning the entire data set? (aka the 'snapshots()' functionality? This would be huge, and I think it'd basically involve the library doing the logic that we'll be doing over and over on the client-side to keep the state of the data set (I'm sure it's more complex than that 🙃 ), and might help down the road for adding Offline functionality? I'd love to use the client as my state management as well.
Wrapping up week 1 of Supabase, and loving it!
Beta Was this translation helpful? Give feedback.
All reactions