Serialize to JSON

1 VersionUtility

Encodes any typed value t as a one-line JSON String. Use it between a typed producer and a textual sink — an HTTP, messaging or log target that expects a string payload rather than a typed value.

How it fits

Typical backends

Tracker output serialised into an HTTP JSON payload.

Smoothed positions serialised and written to a log sink.

Caveats

I/O contractThe JSON mirrors the input type field by field with no flattening, renaming, exclusion or schema stamping, and the result is a single-line document, so pretty-printing must be done downstream.
LimitationThere is no filtering or redaction: any secret, token, internal id or personal data present in the input value is serialised verbatim into the string.
I/O contractEvery message produces a String even when the input value is empty; there is no suppressed-output sentinel.
CostPer-message cost grows with the serialised payload size, and a very large record materialises the whole JSON string in memory before it is emitted.
LimitationNumeric precision, escaping and key ordering follow the platform's JSON encoder and are not configurable on this component.

Versions

0b5648dclatestdefault
live-test prerelease 2026-05-21T00:35:08Z
5/4/2026