[automation] Add basic time-related classes for usage in script and rules #2587
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.
This allows to use DateTime functions a lot easier for users without defining additional imports. We have public methods in different types which makes use of these classes e.g.
openhab-core/bundles/org.openhab.core/src/main/java/org/openhab/core/library/types/DateTimeType.java
Line 170 in a9504bf
openhab-core/bundles/org.openhab.core.model.script/src/org/openhab/core/model/script/actions/Timer.java
Line 76 in a9504bf
org.joda.time
API has a methodDateTime.now().withTimeAtStartOfDay()
which was used by many users. The replacement isZonedDateTime.now().truncatedTo(ChronoUnit.DAYS)
.Duration
class allows easy calculation of differences between two timestamps (Duration.between(Temporal startInclusive, Temporal endExclusive)
-ZonedDateTime
implemetsTemporal
interface).Signed-off-by: Christoph Weitkamp [email protected]