Some functions are directly attached to the eDisGo object while others are not. This leads to an inconsistent API and confusion when navigating the object.
Desired solution
Unify function placement by either attaching all relevant methods to eDisGo or defining a clear pattern (e.g., mixin, module-level utilities).
Alternatives considered
Leaving the structure as-is, but this keeps the API inconsistent.
Additional context
A consistent API improves usability and maintainability.