Skip to content

Anopheles refactor #366

@alimanfoo

Description

@alimanfoo

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:

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions