shexjs / shex.js / 29374493162

75%

Build Type

push

github

Committed by Eric Prud'hommeaux

Commit Message

shexmap: report never-bound variables and unused statics after materialization

A typo'd variable name in a required constraint silently produces an
empty graph: the unbound variable kills every thread needing it, and an
enclosing starred subshape legally absorbs the collapse by taking zero
iterations -- 'success', no quads, no clue (observed: a static keyed
Map:#foo referenced as bp:foo, i.e. Map:#BPDAM-foo).

ThreadedMaterializer now finishes every materialize() -- success or
throw -- with this.lastReport (also attached to MaterializationError as
.report):
- unboundVariables: referenced variables that exist in NO binding frame
  and NO static, each with its TripleConstraint for editor anchoring.
  Benignly-exhausted variables (normal loop-termination dead ends) are
  excluded, so healthy runs report nothing.
- unusedStatics: staticVars nothing referenced -- the same typo seen
  from the other side.

The shexmap app surfaces the report even on successful materialization:
warning squiggles on the affected constraints in the outputSchema pane
and on the unreferenced keys in the statics pane, so a mismatched name
lights up in both editors pointing at each other.  Error anchoring on
MaterializationError merges with the warnings.

Tests: silent-collapse case (empty graph + both report entries with tc
anchoring) and healthy-run quietness; 5046 passing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Coverage Stats

2254 of 3577 branches covered (63.01%)

Branch coverage included in aggregate %.

37 of 38 new or added lines in 2 files covered. (97.37%)

5064 of 6337 relevant lines covered (79.91%)

7024.2 hits per line