Nodes/EasyLoRAMerger/📋 Easy Text Display
ComfyUI Node

📋 Easy Text Display

Read Your Forensic Reports Without Scrolling the Console

By Terpentinas·Created 7 months ago·Updated 4 months ago· 12
📋 Easy Text Display
    • text
    text

    This is the pack's smallest node and probably its most underrated. Every serious node in EasyLoRAMerger - the mergers, the baker, the studios - outputs a forensic_report string, and Easy Text Display is how you actually read those reports without digging through the ComfyUI console. Wire any string into it and the text renders on the node body in the graph.

    That's the whole job, and it's genuinely useful. When a merge produces garbage, the forensic report is where the answer lives: alignment warnings, mismatched trainer flags, sparsity stats. Having that visible in the graph instead of buried in logs turns a debugging session into a glance.

    How it works

    It's a pass-through display node. The text input (any STRING, multiline) gets rendered in the node UI via the standard ComfyUI ui output pattern, and the same text comes out the text output socket. That means you can hang it off a report and also chain the string onward to other nodes if you ever need to. There's nothing to configure - one input, one output, no knobs.

    There's one detail worth knowing: the node also writes the current text back into the workflow JSON when it runs, so the report you're looking at survives saving and reopening the workflow. Stale reports aside, that's a nice touch for keeping a record of what a merge actually did.

    The inputs

    • text - any string. Forensic reports from the mergers, output_path strings, JSON dumps, whatever you need to see.

    Installing it

    Same pack as everything else - Manager (search "Easy LoRA Merger") or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/Terpentinas/EasyLoRAMerger
    

    Restart ComfyUI.

    Gotchas

    There's basically nothing to go wrong here - it's a text box. The only annoyance is the reverse of the persistence feature: because the text gets saved into the workflow, a saved workflow carries an old report even after you've changed the inputs upstream. If a report looks stale, re-run the node. And if you're wondering where to use it first: connect it to the forensic_report output of the Easy LoRA Merger and read what the equalization actually did - that's the single best debugging move in this whole pack.

    CategoryLoRA/Utils

    Inputs (1)

    NameTypeDefaultDescription
    textSTRINGAny text to display — forensic reports, paths, debug output…

    Outputs (1)

    NameTypeDescription
    textSTRING