Any plans to add Local Datastore for JS SDK?

[h4rm]

Are there any plans to add the local datastore to the Javascript SDK just like it happened in the Android/iOS SDK?

While I can save object.toJSON() to the localStorage, the JSON serialization does not recursively save all the other objects that were included in the query but renders out pointers instead.

[andrewimm]

We're actively exploring methods of local storage, so that apps built on platforms like React Native can perform queries when offline. The biggest questions at this point are around how the storage would be interfaced, and whether it would live in the SDK or an addon. For interfaces, the current frontrunner is a Flux-like store based on the one from Parse+React, which fits well in to the new SDK's internal storage scheme. As for where it lives -- the new Controller-based architecture of the SDK makes it really easy to replace individual pieces, and provide functionality as external libraries that are loaded at runtime.

[reidmweber]

👍 We have an iOS app that uses parse and the local datastore. We would like to use parse for a desktop app written with Electron. Ideally, we could use the same methods (pinInBackground, .fromLocalDatastore, etc). Would that work if it was an add-on?

[wookiem]

Any update on availability of a local datastore for React Native?

Also, are you working on any strategies to make query subscriptions more React-like? Unless I'm mistaken, the only way to refresh on-screen data is to re-query the datastore periodically, without any knowledge of whether the underlying data has changed. Thanks!

[carbureted]

+1 on any update regarding a React Native local datastore. Trying to choose between hacking something together on SQLite or integrating parse with the hope that storage is eventually figured out.

Even a negative timeframe like "Not in the next 3 months" would be super helpful.

[yamill]

+1 I think this is much needed - especially for React Native apps.

[5amfung]

Agreed with @carbureted. If local storage is not the priority, please let us know so that we could make a sound decision of what to do.

[andrewimm]

It's not a priority at the moment, because it would take some significant restructuring to provide any valuable querying over local objects. If we were to implement a LocalDatastore similar to the one seen on Android / iOS, it would probably be a redesign version that avoids some of the less performant aspects of pinning. Any API we would implement would also want to be something that works the same way on both React Native and and offline ServiceWorker web apps, so there's a lot of thinking to do here before any action is taken.

[ssssssssssss]

Any progress here? Shall we just need to wrap the native SDKs to achieve this?

[wookiem]

Hi @carbureted. If you happen to use Redux for local storage, you can take
advantage of redux-persist for seamless local storage.

On Wed, Jul 27, 2016 at 3:40 AM, fxwan notifications@github.com wrote:

Any progress here? Shall we just need to wrap the native SDKs to achieve
this?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#77 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG758JjQH0XBGYsq6OpFrn6b13MNHnB-ks5qZwt0gaJpZM4GaGRU
.

[jbeckton]

Since my mobile apps will be written in javascript this is the one feature that is pushing me towards Firebase. Offline support for javascript mobile apps is supported with the Firebase js sdk. It would be great if the Parse Platform team would put a higher priority on this feature as I would rather go with Parse.

[minikin]

I guess it will be also an awesome option for IoT projects.

[cleever]

Any news on this?

[jonas-db]

Thie feature is still missing.

[joshuadiezmo]

I'll wait for this.