-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Bucket Interface to use "in parallel" and resolve promise once #109
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm with 1 nit
index.bs
Outdated
|
||
1. Otherwise, [=/resolve=] |p| with false. | ||
1. [=Queue a storage task=] to [=/resolve=] |p| with |persisted| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I was wondering why we use [=/resolve=]
(with slash) but [=reject=]
(without slash). I think both work in this case, but we should choose one and be consistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, updated for the bucket interface. I'll follow-up for the bucket manager
persist()
is specified on the storage standardPreview | Diff