-
Notifications
You must be signed in to change notification settings - Fork 81
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 the WritableIterable
behavior
#724
Conversation
.then((result) => | ||
expect(result).toEqual({ done: true, value: undefined }) | ||
) | ||
.catch(() => | ||
fail("expected successful done result but unexpectedly rejected") | ||
); |
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.
Changed the behavior for next to return {done: true}
when the writer is closed either due to an error or with call toclose
. This is what I think should be the behavior of Iterables outlined here, based on these two paragraphs:
If an iterator returns a result with done: true, any subsequent calls to next() are expected to return done: true as well, although this is not enforced on the language level.
throw(exception) Optional
A function that accepts zero or one argument and returns an object conforming to the IteratorResult interface, typically with done equal to true. Calling this method tells the iterator that the caller detects an error condition, and exception is typically an Error instance.
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.
👍 Thank you for the work on this.
Once we are sure the DX is solid, we should export the writable from @bufbuild/connect.
Update the
WritableIterable
behavior to improve the developer experience. Writes behave as if they are synchronous and resolve when there is one morenext
call (indicating the previous one is processed) or rejected when consumers callthrow
.