StatifierBlocks.Editor.Findings (StatifierBlocks v0.3.0)

Copy Markdown View Source

The document-level findings panel (ADR-0005 decision 11).

Decision 11 makes the anchor the whole routing mechanism, and the three inline positions - beneath a field, on a slot header, on a block's chrome

  • are rendered by the components that own those positions. What is left for this one is the list view: every finding in the document, in one place, where selecting one selects and reveals its anchor.

Two cases are easy to render wrong and are handled explicitly.

A finding whose anchor names a block id the document does not contain is an orphan. StatifierBlocks.ViewModel collects those separately rather than dropping them, and they are listed here without a reveal control, because there is nothing to reveal. A caller that supplies a finding against a block that has since been deleted sees it, which is the only honest thing to do with it.

Severity is three-valued since the 2026-08-29 amendments, and every source except :lint produces :error. :lint covers both of the others. It renders as a warning for something still compilable and correct once the host acts - the record's example, an invoke type with no registered handler. It renders as :info for something worth the author's attention with nothing wrong at all: the first producer is StatifierBlocks.Datamodel's undeclared-path advisory (amendment 11e-11g), which arrives here rather than through a channel of its own, because 11g says there is no second channel to build.

Nothing in this panel branches on which of the two it is. The severity reaches the markup as a class and a data-severity, exactly as it did when there were two values, which is the property that let a third one be added without touching the list view.

Summary

Functions

Every finding in the document, each one reachable from its entry.

Functions

findings(assigns)

Every finding in the document, each one reachable from its entry.

Attributes