fix: added bucket_id and updated_at on object info #620
Conversation
This file contains 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
ajitsinghkaler
force-pushed
the
object-info
branch
from
6ab1262 to
cec9ea6
Compare
|
Hi @ajitsinghkaler Thanks a lot for the PR! the |
ajitsinghkaler
force-pushed
the
object-info
branch
from
cec9ea6 to
bd178b1
Compare
|
hi @fenos updated the pr. |
fenos
approved these changes
Jan 20, 2025
|
Hero @ajitsinghkaler |
|
🎉 This PR is included in version 1.17.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
What kind of change does this PR introduce?
This is a bug fix in which in Object info did not return bucket_id, last_accessed_at, last_modified which is present in interface FileObjectV2 {
id: string
version: string
name: string
bucket_id: string
updated_at: string
created_at: string
last_accessed_at: string
size?: number
cache_control?: string
content_type?: string
etag?: string
last_modified?: string
metadata?: Record<string, any>
}
What is the current behavior?
In the current behavior bucket_id, last_accessed_at, last_modified were not returned.
#591
#541
What is the new behavior?
In the new behavior these will be returned
Additional context