Skip to content

Conversation

@helloimalastair
Copy link
Contributor

First pass, may need polishing.

{
partNumber: 1,
etag: 'partEtag1',
size: '100',

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we treating size as a string? (Sorry I am no C++/kj expert so maybe it's normal, but it seems a bit odd)

key: string;
uploadId: string;
initiated?: Date;
storageClass?: string;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe strongly type the storage class with a default?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to think on this one a bit more. To my knowledge, we don't already do this for other operations, so might be worth updating them too. Not sure if that constitutes a breaking change though...

- Add range validation (1-1000) for `limit` parameter in `listMultipartUploads`
- Change default limit from 0xffffffff to 0x3e8 (1000) in R2ListMultipartUploadsRequest
- Fix `partNumberMarker` validation to require positive values (p > 0) instead of non-negative (p >= 0)
- Fix `listParts` to pass JWT authentication token to doR2HTTPGetRequest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants