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

Deprecation in favour of ngrx-immer #19

Closed
rainerhahnekamp opened this issue Mar 13, 2021 · 2 comments
Closed

Deprecation in favour of ngrx-immer #19

rainerhahnekamp opened this issue Mar 13, 2021 · 2 comments

Comments

@rainerhahnekamp
Copy link

I had some troubles with ngrx v11. mutableOn always defined the type of the state as unknown. A switch to ngrx-immer solved the problem at once.

What is the difference between these two libraries? If they serve the same purpose, wouldn't it be better to deprecate one?

@timdeschryver
Copy link
Owner

Hi, thanks for the report - I'll have to take a look at why this happens.
The idea behind this library is to add more functionality, but it never happened 😅
Revently, I extracted immer into ngrx-immer so consumers can pick their immer version.

@rainerhahnekamp
Copy link
Author

Thanks for the answer. So I understand that it might be possible that ngrx-etc can get more features than ngrx-immer. Until that, both are "more or less" the same. 👍

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

No branches or pull requests

2 participants