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
The bucket_id, updated_at, lastAccessedAt field of the FileObjectV2 interface is null, although the type definition says it's always a non-null string.
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.
I've already raised this issue in #541 and got closed, but the change didn't fix this. Even more strange is that the last_modified is missing now, which wasn't the case previously, but that field is not marked as non null.
My pr is still not released, because the correct types are nowhere documented other than in storage-js, which seem to be incorrect.
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
The
bucket_id
,updated_at
,lastAccessedAt
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 fields are not checked in the test, though, since the other properties are marked as non null.
Expected behavior
The mentioned fields are 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.
I've already raised this issue in #541 and got closed, but the change didn't fix this. Even more strange is that the
last_modified
is missing now, which wasn't the case previously, but that field is not marked as non null.My pr is still not released, because the correct types are nowhere documented other than in
storage-js
, which seem to be incorrect.The text was updated successfully, but these errors were encountered: