At this time, user(developer) will initialize 'Social module object' in Activity as count of the platform to use.
But we think there are some tiresome of initialize all of module object in one code.
'Initialize in RxSocialLogin' is solution to solve this 'tiresome', but there are so many changes of achieve this solution.
First, we need to remove verbose of RxSocialLogin object by remove their roles.
There some roles which RxSocialLogin have.
Abstract class of ‘Social module object’
Provide helper methods
Manage Config object of ‘Social module object’
So, we can remove first roles by divide to BaseSocialLogin object and make ‘RxSocialLogin` is kotlin object class. Other roles are proper roles of new ‘RxSocialLogin’ object, so we can retain them.
Most important thing of this changes is reducing ‘breaking changes’ while version migration. So, we have to change internal logic, not outside logic.
Affect Version: ??
At this time, user(developer) will initialize 'Social module object' in Activity as count of the platform to use. But we think there are some tiresome of initialize all of module object in one code.
'Initialize in RxSocialLogin' is solution to solve this 'tiresome', but there are so many changes of achieve this solution.
First, we need to remove verbose of RxSocialLogin object by remove their roles.
There some roles which RxSocialLogin have.
So, we can remove first roles by divide to
BaseSocialLoginobject and make ‘RxSocialLogin` is kotlin object class. Other roles are proper roles of new ‘RxSocialLogin’ object, so we can retain them.Most important thing of this changes is reducing ‘breaking changes’ while version migration. So, we have to change internal logic, not outside logic.