Skip to content

doc: documenting how byte arrays are handled when converted to JSON #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
calebschoepp merged 1 commit into from
Feb 4, 2026
Merged

doc: documenting how byte arrays are handled when converted to JSON #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions wit/types.wit
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ interface types {
///
/// This corresponds with the `AnyValue` type defined in the [attribute spec](https://opentelemetry.io/docs/specs/otel/common/#anyvalue).
/// Because WIT doesn't support recursive types, the data needs to be serialized. JSON is used as the encoding format.
///
/// Byte arrays require special encoding since JSON cannot distinguish them from number arrays.
/// They are base64-encoded with a prefix that follows the Data URI RFC 2397 convention:
/// `data:application/octet-stream;base64,<BASE64_ENCODED_BYTES>`
type value = string;

/// An immutable representation of the entity producing telemetry as attributes.
Expand Down