Closed kuceram closed 6 years ago
Interesting, I suppose calling subscribe
with a clone of headers
fix the issue temporary, does it?
Yes it does. But I would suggest to do a clone internally within the subscribe method as method user might not be aware of this. It is also hard to debug this inconvenient.
@kuceram is that ok for you?
Hi, sorry for late respond. I will check it out as soon as possible and let you know. :-)
Works fine, now...
This error happens when you send headers object to subscription method like this:
If you do the second subscription you loose the reference to the first one (callback
destination1
is never called). This issue came due to the fact that you break the atomicity rule: https://github.com/JSteunou/webstomp-client/blob/master/src/client.js#L269You should not manipulate object that are coming from outside.