Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CurrentConsumption doesn't necessarily cover all use cases #95

Open
rsnancollas opened this issue Mar 29, 2024 · 1 comment
Open

CurrentConsumption doesn't necessarily cover all use cases #95

rsnancollas opened this issue Mar 29, 2024 · 1 comment

Comments

@rsnancollas
Copy link
Contributor

I don't think the field names cover all use cases. For example, what does Standby current map to?

I think maybe we should just allow users to specify their own current names

@rsnancollas
Copy link
Contributor Author

Change this to be a slice of struct{current value and current description}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant