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

More sustainable way to store timer values (for charging screen timers) #207

Open
bracyw opened this issue Sep 20, 2024 · 0 comments
Open
Assignees

Comments

@bracyw
Copy link
Contributor

bracyw commented Sep 20, 2024

Description

Currently total times are stored in as values in sessionStorage, to allow for the total time to be saved if the page reloads. However, these timers are not true to the entire charging session. We need a way to have the timers that track charging status's that is actually true. That is either first messages received by the client or preferably values tracked using the server.

Acceptance Criteria

Timers for charging status's (connected to the combined-status-display component) are true to values read from the car.

Proposed Solution

Talk to Reid or Wyatt (Wyatt might need to talk to Wyatt).

Mocks

No response

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

2 participants