Add a base pool class to consolidate the propose_power
and related methods
#922
Labels
part:power-management
Affects the management of battery power and distribution
type:enhancement
New feature or enhancement visitble to users
Milestone
What's needed?
We have 3 different pools now, all using the same interface for managing power, but they don't share a common ancestor, so these methods could eventually inadvertently diverge, which is not what we want.
Proposed solution
Add an abstract base class to define the common interface of all pools so we can ensure they keep the same interface.
It should have at least the
propose_power
andpower
andpower_status
methods.The name might be tricky, maybe
PowerManagingComponentPool
?Additional context
Coming from:
PVPool
implementation #914 (comment)The text was updated successfully, but these errors were encountered: