CrossWS object serialization undesired behavior

[TecToast]

Hello,
as of this PR, CrossWS (at least in NodeJS) automatically sets the binary flag for sending data based on the serialized value (if it is not a string). A normal object gets serialized to a string, so it would be sent as a string, which is what I expected.

However, this changed the behavior (maybe on accident?) by renaming the result of the toBufferLike to dataBuff and the parameter of the function to data (see here), but the typecheck which sets the binary flag still uses the data (the parameter, not the result of the toBufferLike).

Is this the desired behavior? Because now, everything that isn't a string is sent as a blob (if I understand that correctly)

[pi0]

Thanks for proper explanation. It looks like a bug indeed. Can you manage to make a PR to fix perhaps? (and ideally if you can as first commit add a regression test -- it seems we wasn't catching anything regarding binary types)

[TecToast]

Will try that in the next days, thanks for the response!

[pi0]

(feel free to also open an issue there for me not forget)