Skip to content
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

Docs and status for use in ngrx 4.0 #45

Closed
bufke opened this issue Jul 31, 2017 · 3 comments · Fixed by #47
Closed

Docs and status for use in ngrx 4.0 #45

bufke opened this issue Jul 31, 2017 · 3 comments · Fixed by #47

Comments

@bufke
Copy link
Collaborator

bufke commented Jul 31, 2017

I'm trying (and failing) to understand #43 and #41. The readme mentions StoreModule.provideStore which no longer exist. How should this project be used in 4.0? Is it currently not actually compatible and some "very simplistic version as a temporary solution" workaround exists?

@btroncone
Copy link
Owner

@bufke Hello, I apologize for the delay. I have not had the bandwidth lately to update this module. I will do it as time allows or would gladly accept a PR. 👍

@bufke
Copy link
Collaborator Author

bufke commented Aug 8, 2017

Understood. I'll let you know if I find the time. I'd also be happy paying you or anyone else market rate for the work too.

@papaiatis
Copy link
Contributor

+1, need an update for supporting ngrx 4.0

saulshanabrook added a commit to saulshanabrook/ngrx-store-localstorage that referenced this issue Aug 10, 2017
For some reason, we need to manually specify the type of the meta-reducers, as shown in 
ngrx/platform#170 (comment)

Fixes btroncone#45
btroncone pushed a commit that referenced this issue Aug 14, 2017
* Update readme for ngrx 4.0

For some reason, we need to manually specify the type of the meta-reducers, as shown in 
ngrx/platform#170 (comment)

Fixes #45

* Fix readme for ngrx store 4.0

uses fix from #43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants