-
-
Notifications
You must be signed in to change notification settings - Fork 2k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Store Hydration/Serialization API #856
Comments
Remember handling async storage in saving to indexedDB or some native cordova plugin filesystem etc. |
Just throwing out ideas while we're on the topic ... but it would be awesome if something like https://github.com/btroncone/ngrx-store-localstorage became a first class part of ngrx itself. Serializing out for SSR and indexedDB usage is definitely important too, but I would guess that the majority of people are just saving bits of state to localstorage. Plus, the library above doesn't work with feature modules. |
.... When is this going to be implemented? :-( Wasn't it for 7.0?? (today....) |
@brandonroberts When do you think it is going to work? |
@brandonroberts may I take this? |
@brandonroberts sounds great! |
I'm using ngrx-store-sync that I hacked together. Seems to work for my use case. Putting it here to maybe give you some ideas how to do it (or not do it :D) |
@itayod maybe update your article and repo to 8, because of breaking changes in meta reducer |
@rickvandermey Thanks for noticing me! but I think most of the users are still on version 7.X. so I guess update it now could lead to some confusion at this point :) |
Any news on this one? |
Is there any more news? What have you done to contribute. |
@classifieds-dev relax man! I was just asking! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
To better support state serialization and hydration I recommend adding built-in APIs into @ngrx/store. We should try and tackle the two biggest use cases:
Ideally, we would separate the process of persistence and serialization into two steps:
This would allow authors of persistence strategies to focus on persistence without having to reimplement key filtering or Immutable restructuring.
The text was updated successfully, but these errors were encountered: