Conversation
And make onFinish optional
🦋 Changeset detectedLatest commit: 5eb848f The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
| return Boolean( | ||
| this.writableFinished && this.responseStream?.writableFinished, | ||
| ); | ||
| return this.writableFinished && (this.responseStream?.writableFinished ?? true); |
There was a problem hiding this comment.
This is a change in behavior but I believe this is what we want?
conico974
left a comment
There was a problem hiding this comment.
Not sure about the finished() change. The rest is good
| return Boolean( | ||
| this.writableFinished && this.responseStream?.writableFinished, | ||
| return ( | ||
| this.writableFinished && (this.responseStream?.writableFinished ?? true) |
There was a problem hiding this comment.
I'm not sure this one is correct actually.
Your fix is good in case we don't provide a ResponseStream, but in case we do, we may end up in a situation where OpenNextNodeResponse is finished, but not this.responseStream. I'm not 100% sure of that though and not sure what could be the consequences either.
I think we could replace it with
this.responseStream ? this.responseStream.writableFinished : this.writableFinishedThere was a problem hiding this comment.
swapped for your suggestion, thanks!
And make onFinish optional
This is part 1 of 2 in a stack made with GitButler: