Consider abstracting component pool groups into their own class #963
Labels
part:actor
Affects an actor ot the actors utilities (decorator, etc.)
part:power-management
Affects the management of battery power and distribution
type:tech-debt
Improves the project without visible changes for users
Milestone
What's needed?
We have now 2 component pool groups: the default and the shifting group (which sort of move the baseline of the default group). The code could be restructured a bit to avoid some duplication.
Proposed solution
Something like:
Additional context
The original suggestion comes from the PR introducing the groups:
The text was updated successfully, but these errors were encountered: