You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDIT: I just noticed the same issue is with updatedAt, lastAccessedAt
Expected behavior
The bucketId field is not null.
System information
OS: [Arch Linux]
Version of storage-js: [latest main branch state]
Version of Node.js: [e.g. v20.15.1]
Additional context
I've noticed this, while trying to implement the info method for the Dart storage package. Dart is strongly typed so marking it as non-null, while being actually null throws an exception.
The text was updated successfully, but these errors were encountered:
@fenos When using the latest storage docker image v1.11.11 the issue still persists. And in case you've missed it. The same issue is with updatedAt and lastAccessedAt.
Bug report
Describe the bug
The
bucket_id
field of theFileObjectV2
interface is null, although the type definition says it's always a non-null string.To Reproduce
When adding a console.log to the
get object info
test, thebucketId
field is missing.I'm wondering why the bucketId field is not checked in the test, though, since the other properties are.
EDIT: I just noticed the same issue is with
updatedAt
,lastAccessedAt
Expected behavior
The
bucketId
field is not null.System information
Additional context
I've noticed this, while trying to implement the info method for the Dart storage package. Dart is strongly typed so marking it as non-null, while being actually null throws an exception.
The text was updated successfully, but these errors were encountered: