Hi @grant.mccallum
We have changed only 1 thing, and it was a needed bugfix - when we post a message through the web viewer, previously, we were sending whatever type the user has chosen - e.g., if you send the number “1”, we’re sending 1 as a number. Now, we are stringifying everything, meaning that if you send “1”, it’ll be 1 as a string and not as a number. This means that, whoever is receiving or consuming the message, should handle it accordingly.
In the case of “1”, it’s “simple”. But if you decide to send a whole object (e.g., { name: 'John Doe', age: 20 }, then this will be sent/received as a string, and the receiver must cast/parse it to an object and then they can use it as such
Could you please let me know if you have more questions?