feat: Support date type #57
Open
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.
Properly convert date type to arrow object.
Resolves f-677
The PR contains updates to the release notes.Changes
When querying for a field of type
date, we'll properly convert that to an arrow object, whereas prior it has been returned as a dict.As arrow objects ALWAYS include the time, this will result in a date with a time set to midnight (00:00:00).
We don't actually expect an input like
{"__type__": "date", "value": "2023-10-10T09:50:34"}(with time).For local testing or testing against a PR server:
https://github.com/ftrackhq/ftrack-server/pull/1591
Test
Run unit test
test/unit/test_session.py:test_decode_date_and_datetime.Use this code to test manually: