Now not using destructuring because of, what I can only assume, is
"this" style issues. Basically a private member _writableState will be
undefined. Using the object directly fixes that issue
Problem
using destructuring causes FileStreams to have undefined members.
Pivotal issue
Solution
No longer use destructuring and call the WriteStream methods .write and .end directly
Double Checks:
[] Did you update the changelog?
[x] Any new modules need to be exported?
[x] Are new methods in the right module?
[x] Are new methods/modules in core or not (i.e. porcelain or plumbing)?
[x] Do you have good documentation on exported methods?
Change summary:
No longer using destructuring when working with the WriteStream in the putStream callback flow
Steps to Verify:
A bit tough as I needed to consume the library in another app to make sure it worked.
Now not using destructuring because of, what I can only assume, is "this" style issues. Basically a private member _writableState will be undefined. Using the object directly fixes that issue
Problem
using destructuring causes FileStreams to have undefined members. Pivotal issue
Solution
No longer use destructuring and call the WriteStream methods .write and .end directly
Double Checks:
Change summary:
No longer using destructuring when working with the WriteStream in the putStream callback flow
Steps to Verify:
A bit tough as I needed to consume the library in another app to make sure it worked.