fix duration values of "0:60" #1157
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benderl
force-pushed
the
charge-log-migration
branch
from
edc3b4f
to
2572165
Compare
LKuemmel
requested changes
Oct 17, 2023
benderl
force-pushed
the
charge-log-migration
branch
from
2572165
to
00e599d
Compare
|
Konflikte mit dem Master behoben und ein Rebase ausgeführt. |
LKuemmel
approved these changes
Oct 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In der 1.9 wurden Einträge im Ladelog mit 60 Minuten Dauer als "60 Min" gespeichert. Bei der Datenübernahme wurde das durch Parsen als "0:60" übernommen.
Dieser PR verwendet die vorhandenen Zeitstempel für Ladebeginn und -ende, um die Dauer zu berechnen. Dabei wird auf bereits vorhandenen Code zurückgegriffen. Ebenfalls werden vorhandene Ladeprotokolle in
update_config.pyaktualisiert.