Skip to content

readable: Update docs for a case with a binary safe string reading - #5155

Closed
TriAnMan wants to merge 1 commit into
nodejs:masterfrom
TriAnMan:doc-readable-encoding-fix
Closed

readable: Update docs for a case with a binary safe string reading#5155
TriAnMan wants to merge 1 commit into
nodejs:masterfrom
TriAnMan:doc-readable-encoding-fix

Conversation

@TriAnMan

Copy link
Copy Markdown

readable.setEncoding(null) - may be the most preferable way to proxy a binary data without any encoding/decoding overhead

See nodejs/readable-stream#180 for details

@mscdexmscdex added doc Issues and PRs related to the documentations. stream Issues and PRs related to the stream subsystem. labels Feb 9, 2016
Comment threaddoc/api/stream.markdown Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would flip these last two sentences around, or move the new sentence to a separate paragraph.

@jasnell

Copy link
Copy Markdown
Member

LGTM with a nit.

@TriAnMan
TriAnManforce-pushed the doc-readable-encoding-fix branch from d184b48 to eb748a2CompareFebruary 26, 2016 16:03
@TriAnMan

Copy link
Copy Markdown
Author

@jasnell Could you review?

Comment threaddoc/api/stream.markdown Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

useful

@TriAnMan
TriAnManforce-pushed the doc-readable-encoding-fix branch from eb748a2 to 66bb1b4CompareFebruary 29, 2016 09:34
@TriAnMan

Copy link
Copy Markdown
Author

@silverwind thanks! (:

Comment threaddoc/api/stream.markdown Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

very

`readable.setEncoding(null)` - may be the most preferable way to proxy a binary data without any encoding/decoding overhead
@TriAnMan
TriAnManforce-pushed the doc-readable-encoding-fix branch from 66bb1b4 to 174fec5CompareFebruary 29, 2016 09:56
@TriAnMan

Copy link
Copy Markdown
Author

@silverwind Thanks a lot... Seems I need to install a spell checker for my Sublime. (:

@silverwind

Copy link
Copy Markdown
Contributor

Landed in 8d8fef0.

silverwind pushed a commit that referenced this pull request Feb 29, 2016
`readable.setEncoding(null)` - may be the most preferable way to proxy
a binary data without any encoding/decoding overhead
PR-URL: #5155
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
@TriAnMan
TriAnMan deleted the doc-readable-encoding-fix branch February 29, 2016 10:18
@Fishrock123Fishrock123 mentioned this pull request Mar 1, 2016
5 tasks
Fishrock123 pushed a commit that referenced this pull request Mar 2, 2016
`readable.setEncoding(null)` - may be the most preferable way to proxy
a binary data without any encoding/decoding overhead
PR-URL: #5155
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
@MylesBorins

Copy link
Copy Markdown
Contributor

I'm 99% sure this applied to v4. Going to give a day before landing for people to chime in and let me know not to land it

MylesBorins pushed a commit that referenced this pull request Mar 17, 2016
`readable.setEncoding(null)` - may be the most preferable way to proxy
a binary data without any encoding/decoding overhead
PR-URL: #5155
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
MylesBorins pushed a commit that referenced this pull request Mar 21, 2016
`readable.setEncoding(null)` - may be the most preferable way to proxy
a binary data without any encoding/decoding overhead
PR-URL: #5155
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docIssues and PRs related to the documentations.streamIssues and PRs related to the stream subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@TriAnMan@jasnell@silverwind@MylesBorins@mscdex