Well, the MessageEvent’s data object was a JSON encoded string, but as you can see in my socket handler’s code, I parse that. So the resulting “parsed” variable should contain the following information as objects, numbers, and string vales:
{
type: "MESSAGE",
data:
{
topic: "channel-bitsevents.32945820",
message:
{
user_name: "nifty255",
bits_used: 100",
etc: "and so on"
}
}
My guess is the object doesn’t have the structure the docs say it has.