DOGMA EmptyReview 1.0.23

Take the description literally: this node takes no inputs and outputs an empty review. That's it. It is the least glamorous node in the pack and it exists because of a real, boring problem - a DOGMA_REVIEW is a typed socket, ComfyUI validates types on queue, and a review viewer downstream does not care whether the review is empty as long as it is a review.

So: what is a DOGMA_REVIEW? In this pack's 1.0.23 line, the phase-3 render node can save side-by-side comparison images as it works - before/after per category, the applied crop, the raw generated crop, the inpaint and blend masks - into a temp directory, and it hands back a review dictionary that points at those files. DOGMAReviewPairV123 is the viewer: you give it a review, a category index, a crop index and a view name, and it loads the two PNGs you asked for and returns them as images.

The awkward moment arrives when you want the viewer wired up but no review to show. Two common cases. You built the review part of the graph on a branch where phase 3 does not run, or you turned save_comparisons off on the render node because you were doing a batch and did not want the temp PNGs. Both leave you with a dangling viewer input and a graph that will not queue.

schema=1, enabled=False, categories=[] is the shape EmptyReview emits, and it is exactly the shape the viewer expects from a render that produced nothing to compare.

Inputs and outputs

None in, one out: DOGMA_REVIEW, disabled and empty. That's the whole contract.

Using it

Wire it into DOGMAReviewPairV123's review input whenever the real review is not coming from this particular run. The viewer will then return its empty-image path and set the details output to a plain explanation - literally Confronti disattivati. ("comparisons disabled") when the review it received reports enabled=False. Nothing crashes, nothing renders, and the label in the UI says the comparisons are off rather than showing you a stale pair.

That last detail is the point of the node being honest about its own emptiness instead of just emitting an empty dict. If EmptyReview reported enabled=True, the viewer would try to index into an empty category list and you would get the "no category in this slot" error instead of the correct "comparisons are off" message.

Install

Ships with the rest of the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/axior/ComfyUI-DOGMA-Nodes

Manager users: search DOGMA Nodes. The pack's requirements.txt lists only scipy>=1.10, and this node in particular needs nothing at all - no model, no scipy call, no temp file. Restart ComfyUI after cloning so the node class registers.

Should you actually use it

Yes, in one specific situation, and it is worth being blunt about which: leaving a review viewer permanently in your graph while you switch between "render with comparisons" and "render without." Toggling save_comparisons on the render node is the normal way to work - comparisons cost you a few PNG writes per job and a growing temp folder - and without a stub you end up rewiring the review socket every time you toggle it. One node in a bypassed branch, or a saved template with it inline, removes that chore.

If you never use the comparison viewer, ignore this node entirely. It does nothing you can see, and its front matter in the pack is a single class with a two-line body - there is no hidden behaviour to discover.