Allow to bypass stringification of publish payload

[edzis]

I am migrating our browser client from aws-iot-device-sdk to aws-crt/dist.browser/browser/mqtt and need to send a Uint8Array payload because the other end expects that. Unfortunately

aws-crt-nodejs/lib/browser/mqtt.ts

Line 328 in 8b8195c

let payload_data = normalize_payload(payload);

converts the payload to a string format.

I am not aware any reasoning in favor of stringification and am not challenging that. However I would like to have a way to bypass that.

A custom implementation could be passed in MqttConnectionConfig or overwritten as a static function of MqttClientConnection or MqttClient.

[edzis]

And maybe you could point me to some argumentation for the use of this normalization? Maybe we are just bending the best practices with our usage.

[graebm]

Fixed in latest releases of aws-crt and aws-iot-device-sdk-v2

[graebm]

To bypass stringification pass an ArrayBuffer, or some ArrayBufferView such as Uint8Array or DataView