This makes the JSON examples in the PubSub documentation follow the JSON
standard of only having a value-separator (a comma) inbetween object
members and not at the end of the member list
This fixes issue #636 because it seems the websocket servers don't like parsing trailing commas and the documentation examples might as well contain valid JSON.
This makes the JSON examples in the PubSub documentation follow the JSON standard of only having a value-separator (a comma) inbetween object members and not at the end of the member list
This fixes issue #636 because it seems the websocket servers don't like parsing trailing commas and the documentation examples might as well contain valid JSON.