Remove message content from JS client logging

[JamesNK]

#1449

[analogrelay]

Looks good to me. @davidfowl if you want to introduce a flag to re-enable this, file an issue for that and we can track it later. This change is required to ship though, so I'd rather get it in ASAP.

[davidfowl]

Looks good to me. @davidfowl if you want to introduce a flag to re-enable this, file an issue for that and we can track it later. This change is required to ship though, so I'd rather get it in ASAP.

Ummm, naw. See the problem is when you use binary you can't really use any other tools to look at the data, so I think the flag has to be added along with the feature.

[JamesNK]

Where should the flag exist? How does a dev set it?

[davidfowl]

Where should the flag exist? How does a dev set it?

All of our ts flags are currrently on an options object passed into the hubConnection constructor. I imagine it would go there.

[analogrelay]

See the problem is when you use binary you can't really use any other tools

What do you expect our logging to output? Base64? Hex?

[davidfowl]

LGTM I was concerned about logging after messages were deserialized by the hubconnection.