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

4.1.0 Release #198

Closed
bjohnso5 opened this issue Apr 26, 2018 · 4 comments
Closed

4.1.0 Release #198

bjohnso5 opened this issue Apr 26, 2018 · 4 comments

Comments

@bjohnso5
Copy link

Wondering if it's possible to have a 4.1.0 release prepared with the recently merged digest debounce changes included.

It's a feature my team is very excited about integrating into our application.

Cheers!

@AntJanus
Copy link
Collaborator

AntJanus commented May 2, 2018

The issue in #196 is holding up a new release and I think none of the contributors (including me) have the bandwidth to tackle it. If either of you would like to contribute to the fix, even just getting it started and leaving it for someone else to finish, that would be appreciate and will speed up the publishing process.

@bjohnso5
Copy link
Author

bjohnso5 commented May 3, 2018

@AntJanus I'll see if I can dive into it sometime in the next couple of days

@piehouserat
Copy link

I know everyone is super busy but eagerly awaiting the next release that has the digest debouncing stuff. We've pretty much converted our whole app to use redux & ng-redux and while we are much happier with the state of the code and our ability to move to react fairly easily, the performance has suffered as we dispatch quite a lot of actions.

Is there any way to somehow get this code into my app ASAP - I don't suppose I can simply download a zip of the master branch and overwrite the contents of the ng-redux node_modules dir?

@AntJanus
Copy link
Collaborator

AntJanus commented Jul 9, 2018

@piehouserat you could, you'd just have to make sure you compile it first. I can go ahead and release what we have under like a 4.1.0-alpha release. Would that work?

Honestly, we just need to fix that dev tools compat issue and I'm ready to release it. The other items on the release list #204 aren't as important.

Closing this in favor of #204

@AntJanus AntJanus closed this as completed Jul 9, 2018
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

3 participants