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

Interval deserialization fix #83

Merged
merged 3 commits into from
Dec 31, 2019
Merged

Conversation

insightindustry
Copy link
Owner

#80: Revised how the default deserializer functions for datetime.timedelta and datetime.datetime objects functions. When deserializing either, the default deserializer now starts by attempting to coerce the value to a datetime.timedelta using the Validator Collection timedelta() validator function, which supports the expression of amounts of time as both integers (e.g. 23 seconds) and strings (e.g. 00:00:23). If the object cannot be converted to a timedelta (if it is a complete / proper datetime with both a time and date value), the default deserializer will then revert to returning a datetime.datetime object.

@insightindustry insightindustry added this to the 0.5.1 milestone Dec 31, 2019
@insightindustry insightindustry self-assigned this Dec 31, 2019
@insightindustry insightindustry merged commit b5e491a into develop Dec 31, 2019
@insightindustry insightindustry deleted the interval-deserialization-fix branch December 31, 2019 20:30
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.

1 participant