-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
stream: minor fix for ReadableState #11139
Conversation
It seems that the comments for sync flag of ReadableState is copied from WritableState without modification.
@nodejs/streams |
Given that this removes a property, this is potentially semver-major. It shouldn't be, but we need to be certain. |
I think we are going to release this as semver-minor in
|
Landed as 1004b9b and 202b07f |
flag `ranOut` became unused since 0f8de5e, but 0f8de5e did not remove it. PR-URL: #11139 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
It seems that the comment for sync flag of ReadableState is copied from WritableState without modification. PR-URL: #11139 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
@mcollina Just ICYMI, our current policy is that at least 2 CTC members need to sign off on semver-major changes before landing them. I don’t think that’s a problem here because it’s not something that’s really covered by our API (as you pointed out)… I just added the label because, at least from Node’s perspective, I don’t think there’s a reason to not consider this semver-major. |
Oh, I thought this was sitting there for a while, and just reduced the pull requests count by one. |
remove unused flag
ranOut
from ReadableState,ranOut
had been unused since 0f8de5efix the comments for flag
sync
of ReadableState.Checklist
make -j4 test
(UNIX) passesAffected core subsystem(s)