-
Notifications
You must be signed in to change notification settings - Fork 26
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
Anopheles refactor #366
Comments
We could do this using something along the lines of the mixin pattern (e.g., here). E.g., we could have classes like class AnophelesDataResource(
AnophelesPca,
AnophelesH12,
AnophelesHaplotypeData,
AnophelesSnpData,
AnophelesCnvData,
AnophelesMetadata,
AnophelesBase):
.... Potential complexity here is that some of these mixin-style classes would depend on others. E.g., the |
The
AnophelesDataResource
class is becoming a God class, there are a large number of methods covering different areas of functionality, and it is becoming unwieldy and hard to navigate and maintain.Propose to refactor this somehow, compartmentalising different areas of functionality into separate classes.
This could be addressed in stages, breaking out different areas of functionality in different PRs:
The text was updated successfully, but these errors were encountered: