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

Worried about future compatibility #61

Closed
abductedMind opened this issue Dec 29, 2018 · 2 comments
Closed

Worried about future compatibility #61

abductedMind opened this issue Dec 29, 2018 · 2 comments

Comments

@abductedMind
Copy link

abductedMind commented Dec 29, 2018

There is evidence that this project is losing steam or at least is vulnerable to not being made compatible with future versions of Angular when they come out. The example app not being up to date is my biggest clue to this possible future. How can the public know that this repo will likely continue to be maintained? NgRx is looking like a better choice if one wants to move with updates to Angular.

@smithad15
Copy link
Member

Thank you for your concern about the livelihood of this project. Like the majority of open source projects, this is maintained by a team of volunteers who try our best. However we all have jobs, families, and other commitments in our lives that also take our time and attention.

The example app, and truly this whole project, is slowly being updated after a period of low maintenance. This can be seen by the existence of this mono-repo. As to the specifics of the example application, please see #55 and https://github.com/angular-redux/platform/tree/upgrade-angular-7 where upgrade work is in progress.

In regards to future compatibility, the core functionality of this package (hooking up Redux with Angular) is a very simple API that does not have a lot of exposure to the Angular APIs. Because of this, there is quite often very little we have to do to support the latest version of Angular (In fact, version 9 supports both Angular 6 and 7). There have been a couple of times where the only thing we needed to change for basic compatibility was the peer dependency versions in our package.json. Yes, I will admit that there is more that we can do and we hope that we can add those features in, or that caring members of the community like yourself, would contribute your help through PRs and constructive suggestions.

With respect to NgRx, we are quite happy to exist within the same Angular community ecosystem. Both packages provide their own ways to implement a central state store. The more solutions that are available, the better it is for developers to choose the correct tool for their specific problem space.

Thank you again for the concern and I hope to see your name on a PR soon.

@abductedMind
Copy link
Author

I appreciate the response! My preference for this package was founded in the less can be more philosophy. For example having to learn about and find Reselect instead of taking it for granted within NgRx was beneficial. Additionally if one uses both React and Angular this package is a better choice imo because you can embrace the larger Redux ecosystem more directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants