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

Remove old redux utility methods #7952

Closed
charrondev opened this issue Oct 19, 2018 · 0 comments · Fixed by #9800
Closed

Remove old redux utility methods #7952

charrondev opened this issue Oct 19, 2018 · 0 comments · Fixed by #9800
Assignees
Labels
Domain: Refactoring Type: Technical Debt A Lannister always pays his debts. Eventually.
Milestone

Comments

@charrondev
Copy link
Contributor

charrondev commented Oct 19, 2018

With the completion of #7910 we have new class based redux utilities.

The old module exported function utilities still need to be cleaned up. They should be removed and instances using them converted to using the new classes. This is primarily the rich editor reducers and the authentication reducers.

Acceptance criteria

  • The functions in @libary/redux/utility should all have their usages removed, and the file should be deleted.
@charrondev charrondev self-assigned this Oct 19, 2018
@charrondev charrondev added Type: Technical Debt A Lannister always pays his debts. Eventually. and removed Type: Enhancement A planned, actionable feature or improvement to one Type: Bug A clear defect in a feature that has been shipped. Fix should include automated testing if possible. Domain: Technical Debt labels Apr 30, 2019
@charrondev charrondev added this to the 2019-12-11 ts milestone Nov 28, 2019
@charrondev charrondev assigned NeenaDev and unassigned charrondev Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Domain: Refactoring Type: Technical Debt A Lannister always pays his debts. Eventually.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants