Skip to content

Conversation

@cynron
Copy link
Contributor

@cynroncynron commented Feb 3, 2017

  1. remove unused flag ranOut from ReadableState, ranOut had been unused since 0f8de5e

  2. fix the comments for flag sync of ReadableState.

Checklist
  • make -j4 test (UNIX) passes
  • commit message follows commit guidelines
Affected core subsystem(s)
  • stream

Wang Xinyong added 2 commits February 3, 2017 14:31
flag `ranOut` became unused since 0f8de5e, but 0f8de5e did not remove it.
It seems that the comments for sync flag of ReadableState is copied from WritableState without modification.
@nodejs-github-botnodejs-github-bot added the stream Issues and PRs related to the stream subsystem. label Feb 3, 2017
@cynroncynron changed the title Minor fix for ReadableStatestream: minor fix for ReadableStateFeb 3, 2017
@addaleax
Copy link
Member

@jasnell
Copy link
Member

@nodejs/streams

@jasnell
Copy link
Member

Given that this removes a property, this is potentially semver-major. It shouldn't be, but we need to be certain.

@addaleaxaddaleax added the semver-major PRs that contain breaking changes and should be released in the next major version. label Feb 3, 2017
@mcollina
Copy link
Member

@mcollina
Copy link
Member

I think we are going to release this as semver-minor in readable-stream. If that does not cause issues, we can release this as semver-minor also in Node.

ReadableState is undocumented atm.

@mcollina
Copy link
Member

Landed as 1004b9b and 202b07f

@mcollinamcollina closed this Mar 3, 2017
mcollina pushed a commit that referenced this pull request Mar 3, 2017
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]>
mcollina pushed a commit that referenced this pull request Mar 3, 2017
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]>
@addaleax
Copy link
Member

@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.

@mcollina
Copy link
Member

Oh, I thought this was sitting there for a while, and just reduced the pull requests count by one.
Thanks for noting.

@jasnelljasnell mentioned this pull request Apr 4, 2017
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver-majorPRs that contain breaking changes and should be released in the next major version.streamIssues and PRs related to the stream subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@cynron@addaleax@jasnell@mcollina@nodejs-github-bot