-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Draft & dummy implementation of account removal #274
Conversation
Please let me know your thoughts on current dummy implementation. |
Changes Unknown when pulling a9cf89b on fedys:issue-103 into * on cross-solution:develop*. |
I like the concept to push the responsibilities of listing and removing dependent items to the modules. And although it is tempting for its simplicity to use a static method as factory, we should use dedicated factory classes, because of SoC principle. |
Changes Unknown when pulling a6c8a3c on fedys:issue-103 into * on cross-solution:develop*. |
@TiSiE |
Looks good, go ahead! 😃 |
Let me know if you are happy with the current implementation of related objects listing. If yes, I will supply unit tests and then we can move to the second step, related objects removal. |
Changes Unknown when pulling b29839f on fedys:issue-103 into * on cross-solution:develop*. |
Code is alright. @cbleek must review the UI |
Changes Unknown when pulling 73add93 on fedys:issue-103 into * on cross-solution:develop*. |
Am 24.08.2016 um 17:09 schrieb Mathias Gelhausen:
Regards, Carsten |
Changes Unknown when pulling 923774a on fedys:issue-103 into * on cross-solution:develop*. |
* pr-274: Implement user account removal Implemented removing of related objects for account removal refs gh-103 Unit tests for account removal object listing refs gh-103 Real implementation of account removal object listing refs gh-103 Refactorized dummy implementation of account removal refs gh-103 Draft & dummy implementation of account removal refs gh-103 Close #103, #274
refs gh-103