Refactor how pumptools handles options internally because it's currently centralized a single option module for each hook with a lot of code duplication.
Detailed description
This is based on an old concept that was also used in bemanitools. The current implementation in bemanitools is not perfect but a good basis to iterate on and make something that fits nicely into pumptools. Key items are:
Have option structures with each module requiring option exposure
Allow overriding of config file options via command line args
Simplify option/command args handling
Add unit tests (about time to get started somewhere with that...)
Benefits
Architecture improvement reducing code duplication and increase maintainability
In GitLab by @icex2 on May 9, 2020, 18:19
Summary
Refactor how pumptools handles options internally because it's currently centralized a single option module for each hook with a lot of code duplication.
Detailed description
This is based on an old concept that was also used in bemanitools. The current implementation in bemanitools is not perfect but a good basis to iterate on and make something that fits nicely into pumptools. Key items are:
Benefits
Architecture improvement reducing code duplication and increase maintainability
Drawbacks
Touches a lot of modules in the code base
Current blockers
None