Investigate the way to work with Schemas and unleashing the whole power of Realm

[adrienthiery]

No description provided.

[Kabangi]

@adrienthiery Could you please write down your thoughts on this, I would want to be part of this project. Wondering how you thinking about this issue:- i.e schemas, encryption, pub/sub and migration support

[adrienthiery]

Hi @Kabangi ,
My leads would be to check how actually redux-persist is calling the adapter to see if we could pass additional infos like the schema or how if we could override the methods to store and restore.

But to be honest, I am using Realm only as a local database, not with its' server counterpart.

[Kabangi]

I think supporting the server counterpart will really introduce so many issues.

My use cases is to support realm as a local cache with encryption support and nothing more.

My initial thought for this was probably passing redux-persist interface implementation that depends on a realm singleton to the store. Then expose the construction of the singleton to the user with a configuration options such as schema, encryption key, migrations etc.

In regard to "how if we could override the methods to store and restore." I have no idea how to go about this.

I will be forking your repo over the weekend and play around with it.

[eduardojunio]

@Kabangi my use case is the same as yours. How would you expose the construction of the singleton? This is my fork: https://github.com/eduardojunio/redux-persist-realm, I removed the singleton, I'm exporting a constructor function that does nothing actually, I did this because I was trying to export a singleton constructor as you said, but I don't came up with any ideia on how to do it.