Tcp request node default behaviour changed from V2 to V3

I have just realized that in nodered version 3 there is a new option in the "tcp request" node: reattach delimiter. That option did no exist in nodered version 2, and in version 3 in unchecked by default, while the default behaviour in version 2 was to reattach the delimiter. The result is that flows that were working in nodered V2 will not work in V3 until you find that you have to enable the "reattach delimiter" option.
My suggestion would be to change the default value to reattach the delimiter to be consistent to nodered v2.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.