| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| * `error` {boolean|undefined} | ||
| * `readable` {boolean|undefined} | ||
| * `writable` {boolean|undefined} | ||
| * `signal`: {AbortSignal|undefined} | ||
| * `signal` {AbortSignal|undefined} | ||
| * `cleanup` {boolean|undefined} If `true`, removes the listeners registered by | ||
| this function before the promise is fulfilled. **Default:** `false`. |
There was a problem hiding this comment.
Don't think that the convention for options parameter types is to include undefined?
Sorry, something went wrong.
There was a problem hiding this comment.
IMO that's an issue for a different PR because this PR follows the same convention as the rest of the parameters.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Please check my working, but my reading of stream.finished() and stream.promises.finished() is that:
When options.cleanup was added in #44862, the documentation for it appears to have been added to the callback API function rather than the promises API function.
This change moves it to the correct place, and documents the context of its usage, similar to the equivalent documentation for the callback API function.
Refs: #44862