Enum Document 

pub enum Document {
    Ts(TsProgram),
    Toml(TomlDocument),
    Json(String),
    Js(String),
    SourceMap(String),
    DebugSidecar(String),
}

One typed output document. No String at construction for TypeScript or TOML content (R7.8) — Json/Js/SourceMap/DebugSidecar stay opaque payloads because bynk-emit never re-parses them itself, not because they’re an escape hatch from the rule.

Variants

Ts(TsProgram)

A generated TypeScript module. Every bynk-emit construction site builds this today by wrapping its still-String-producing content in one TsStmt::verbatim(VerbatimOrigin::NotYetConverted, ..) — see that variant’s own doc comment for why each site does this literally, rather than through one shared helper.

Toml(TomlDocument)

wrangler.toml, still as the real tree emit_wrangler_toml built — printed only at the bynk-driver write boundary.

Json(String)

Generated JSON with no tree this compiler tracks yet (package.json, tsconfig.json, the contracts/secrets manifests).

Js(String)

Type-stripped JavaScript (bynk-strip::strip_project_to_js’s own output) — never produced by bynk-emit itself, which only ever builds Ts; kept distinct from Ts so a stripped artefact never round-trips back through the TypeScript printer/lint.

SourceMap(String)

A source-map v3 document, split out of its originating file’s own staged source_map at the sibling path write_output names it (<file>.map).

DebugSidecar(String)

The handler-label debug sidecar, split out the same way at <file>.bynkdbg.json.

Implementations

impl Document

pub fn text(&self) -> String

This document’s own text, whichever kind it is — for read-side callers that only need bytes (golden fixtures, bynk-strip’s own need to feed Ts content through strip_types, bynk-wasm’s JS-facing API, in-process test helpers). Ts/Toml print through the same printer bynk-driver::output::write_document writes from (R7.3/R7.6) — this is a rendering, not a second construction path; nothing here builds a Document from a String.