Expose modify_time on LPath - #606
Merged
Merged
Conversation
This file contains hidden or 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
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.
Summary
Exposes the
modify_timemetadata field onLPath, following the same pattern as the existingversion_id,content_type, andsizegetters.Changes
modify_time: Optional[datetime]to the internal_Cache.modifyTimefromldataObjectMetain thefetch_metadataGraphQL query.datetime(normalizing a possibleZsuffix, sincedatetime.fromisoformatonly supports it on Python 3.11+, while the SDK targets>=3.9).modify_timein_clear_cache.modify_time(*, load_if_missing=True) -> Optional[datetime]getter mirroringversion_id.2.76.9and added a changelog entry.Usage
Notes
The backing column
modify_time(timestamp with time zone) exists onapp_public.ldata_object_metain vacuole and is exposed by Postgraphile asmodifyTime.