fix(form-engine): a read row with an object value names it and previews its keys - #125

What

A FormEngine read row whose value is a data provider summarised it as 11 fields — a count that reads like a string and says nothing about which provider the value is. Reported by Filip on qorus-ide Qlip builds #204–#208 (Components/Variables/Editor · Read Only Variable: "Initial value says 11 fields like it's a string or something — we need to better visualize it's actually an object / a complex value").

Two changes in the read-first engine:

• readFirst.ts — formatDataProviderValue names a provider the way the picker shows it: kind · name · path (datasource · omquser · /bb_local). formatOptionValue uses it for the data-provider type before falling back to the key count.
• CompactRow.tsx — the hash row's structured preview now also applies to rows whose declared type holds a plain object: data-provider, options, system-options, processor-mappings. The list is explicit because a schema or richtext value is an object too and already has a preview of its own. Develop's rule that an expression stored as an AST is never previewed as a hash applies to these rows as well.

A string row gets no preview — the preview follows the shape of the value, not the read mode.

Before / after

Before: Initial value 11 fields
After: Initial value datasource · omquser · /bb_local with type / name / transaction_management / path / … one Show more away.

Coverage

• __tests__/readRowObjectValue.test.tsx — the reported case (names the provider, previews its keys, and the scalar row beside it stays one line).
• __tests__/readFirst.test.ts — formatDataProviderValue shapes.
• Story Form/Engine/FormEngine → Compact Read Only Data Provider with a play asserting the same three things; Qlip picks it up as a new snapshot.

Version

0.10.56 (last published beta is 0.10.55).

Follow-up in qorus-ide

Bump reqraft once this is released, then accept the Variables Read Only Variable capture that has carried Filip's rejection since build #204.