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

Add support for TimePeriodType relative EndTime #18

Merged
merged 1 commit into from
May 9, 2024

Conversation

DerAndereAndi
Copy link
Member

If only EndTime is provided and it is a duration, it has to decrease over time. To do this without actually changing the data, it will always be transformed into an absolute time in Marshal and returned as an up to date relative duration in Unmarshal and a helper method

Fixes #12

If only EndTime is provided and it is a duration, it has to decrease over time. To do this without actually changing the data, it will always be transformed into an absolute time in Marshal and returned as an up to date relative duration in Unmarshal and a helper method

Fixes #12
@coveralls
Copy link

Coverage Status

coverage: 92.849% (+0.06%) from 92.786%
when pulling f98bda8 on feature/timeperiodtype-update
into 0b4b37a on dev.

@DerAndereAndi DerAndereAndi merged commit e636ba0 into dev May 9, 2024
6 checks passed
@DerAndereAndi DerAndereAndi deleted the feature/timeperiodtype-update branch May 9, 2024 17:39
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

Successfully merging this pull request may close these issues.

Handle TimePeriodType Endtime being a relative value
2 participants