Conversation
kennytm
left a comment
There was a problem hiding this comment.
it is a bad idea to have behavior-changing arguments hidden inside the context.
Use context Values only for request-scoped data that transits processes and APIs, not for passing optional parameters to functions.
Then shall we add another contextual generic param instead of put them in the context? |
|
we should put these into an options struct but there's no need to make a storage-specific it's easy to determine the common options between S3, GCS and local storage:
the return value of (but perhaps we could just automatically issue N requests to get rid of both page size and page token) |
Co-authored-by: kennytm <kennytm@gmail.com>
kennytm
left a comment
There was a problem hiding this comment.
LGTM, though ideally we should get rid of ListCount.
|
LGTM |
|
cherry pick to release-4.0 failed |
* storage: update WalkDir Co-authored-by: kennytm <kennytm@gmail.com>
What problem does this PR solve?
resolve #463 (comment)
move
dirlistCountparameters into contextWhat is changed and how it works?
update WalkDir api
Check List
Tests
Related changes
Release Note