Display String Data

Somewhere around the third JSON blob you've wired into an opaque pipeline, you realize the workflow has no way to show you what's inside it. That's what this node is for. Display String Data takes any string - JSON, YAML, CSV, or a wall of raw text - and pretty-prints it in a preview you can actually read, then hands the (possibly reformatted) string back out for the rest of the graph.

How it works

It's the debugging end of this pack's string pipeline. With display_pretty_enabled on (the default), the node tries to pretty-print the input based on string_format_determination:

• AUTO_DETECT (default) tries formats in order - JSON, then YAML, then CSV - and uses the first one that parses.
• JSON / YAML / CSV forces a specific format, skipping auto-detection.

JSON gets json.dumps with 4-space indent (and optional key sorting); YAML gets the same safe-dumper treatment the pack's converter uses, with multiline strings as literal blocks; CSV gets each row joined with ", ". Whatever it produces is shown in a PreviewText widget and returned from the node. If nothing parses, or pretty display is off, it just passes the raw string through unchanged.

The AUTO_DETECT order is the one thing to remember: if your JSON is malformed but happens to be valid YAML (not uncommon - YAML is lenient), you'll get YAML output and maybe not notice. Forcing a format kills that ambiguity.

Inputs and outputs

• input_string - anything.
• display_pretty_enabled - default on.
• string_format_determination - AUTO_DETECT / JSON / YAML / CSV.
• sort_enabled - sorts keys, default off.

Output is Output String, with a pretty-printed preview widget when applicable.

Why it earns its place

It's the natural terminal for everything this pack produces: hang one off ConvertCsvToJson, JsonValueMutator, or HttpRequestSender's response output and you can actually see what your pipeline is doing instead of trusting it. Because it's an output node, it always runs and works backward from the graph's cache - which makes it a great canary when you suspect a node upstream is misbehaving. If a response looks wrong, drop one of these on it and watch.

Install

ComfyUI Manager → search "comfy-nekonote-extensions", or:

cd ComfyUI/custom_nodes
git clone https://github.com/0nyx-networks/comfy-nekonote-extensions

Restart ComfyUI; it's under NEKONOTE → Text. It's part of the MIT-licensed utility pack by MINETA "m10i" Hiroki (v0.4.7) - no models, no heavy deps (pyyaml does the YAML work and is already in most installs). The pack targets the newer comfy_api.latest backend API, so if the node never shows up, update ComfyUI before you start debugging anything else.