Blinking/Uncatching Behaviour about reactfire HOT 6 CLOSED

I could see that working really well, and best of all would be framework agnostic. This kind of client-side caching seems almost like an absolute necessity when pulling information to build the state of an app, when the network can be slow or unavailable.

from reactfire.

Thanks for opening this issue! I'm a bit overwhelmed with other things at the moment, so give me a few days to process this and respond in full. I just wanted to let you know that I read it and am not ignoring it.

FYI, the original source code is just in a single file here. Local setup instructions are here.

from reactfire.

I think that this is an excellent idea for app resiliency (especially given the promising feature-set of GunJS!), but that if it were to exist, it should probably exist within the Firebase binding and not in ReactFire as in theory it could work without any knowledge of an implementing client.

from reactfire.

@antoligy it could be a wrapper or a plugin, like firebaseResillent = new FirebaseResillent(firebase) or something the like; where you modify the main object.

from reactfire.

@antoligy maybe we should probably bring this to the actual firebase project; rather than reactfire since that, as you say, it doesn't have to be just about ReactFire.

I'd just be more complex that way, and I don't think I could develop that on my own (considering work).

Maybe a generic wrapper would be nice, where you can say which functions do what; and make it external from firebase so that it can work with other libraries as well that use this JSON model.

from reactfire.

Hey there, thanks for the discussion so far. I agree that this seems like more of a thing that belongs in the core Firebase SDK, not ReactFire. Unfortunately, the core Firebase SDK is not yet open sourced, so for now, you'd have to build a wrapper around the SDK which has this behavior. Note that we have longterm plans to bring true offline persistence to the JavaScript SDK like we have with the mobile SDKs, but it is still a good deal off.

Marking as "invalid" just because this isn't the right place to introduce this kind of behavior. I definitely would love to see you make something like this, but I think it should live independent of ReactFire.

Let me know if you've got questions.

from reactfire.