Deprecate Readable.readableFlowing setter
#39495
Comments
Readable.readableFlowing setter
Readable.readableFlowing setterReadable.readableFlowing setter
|
I'm +1. I think I added it because we needed it somewhere in core. |
|
There might be one case where it makes sense to have it: https://github.com/nodejs/undici/blob/main/lib/client.js#L723-L733 Not sure how we could work around that. Maybe change undici so it uses |
|
It is also used in : Line 523 in 533cafc Line 719 in 533cafc Line 384 in 533cafc node/lib/internal/child_process.js Line 438 in 533cafc |
|
It's probably easier to keep using it there than fixing it. I'm more concerned with the public api to our users. |
ronag
mentioned this issue
Mesteery
linked a pull request that will
close
this issue
|
How about the evolution of this implementation? |
|
Have something who I can help? Some guidance could be great |
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue
randomhash
mentioned this issue


How this works and what it does is pretty undefined and I don't think users should be using this setter.
The text was updated successfully, but these errors were encountered: