Finding from promo-video production recon (internal ref: steedos-labs/video-studio#61). Not claiming; filing for triage.
Environment
@objectstack/*17.1.0 (hotcrm reference app, hotcrm @ a76b69ff003605e0d1512c4bbf304031bb5c5fec, dev server)- Page written via metadata API into a fresh writable package (
PUT /api/v1/meta/page/<name>?mode=draft&package=… → publish-drafts)
Actual
In a kind: 'html' page, <list-view> renders the row count (e.g. "23 records") and the filter/group/sort toolbar, but no data columns at all — only the index column. Eight binding forms all tried, none renders columns:
- JSX array literal for
columns - JSON-string
columns - object-array
columns ({field, label}) viewName reference to a saved viewview reference to a saved view- child
<column> elements - no
columns at all (default-columns expectation) - kebab/camel attribute-name variants of the above
Expected / contrast
The same block in a kind: 'react' page works fully: <ListView columns={['name','stage','amount','close_date']}> renders all four columns (Opportunity Name / Stage / Amount / Close Date). So the data path and the block itself are fine — the html-tier attribute → prop binding for columns appears to be dropped.
Impact
Any html-tier page (the "parse, never execute" tier meant for AI-drafted/unreviewed pages) cannot show a usable data table — rows without columns. Not a P0 for us (we re-scoped the demo page), but it undercuts the html tier's headline use case of safely accepting AI-authored pages that include data blocks.
Finding from promo-video production recon (internal ref: steedos-labs/video-studio#61). Not claiming; filing for triage.
Environment
@objectstack/*17.1.0 (hotcrm reference app, hotcrm @a76b69ff003605e0d1512c4bbf304031bb5c5fec, dev server)PUT /api/v1/meta/page/<name>?mode=draft&package=…→publish-drafts)Actual
In a
kind: 'html'page,<list-view>renders the row count (e.g. "23 records") and the filter/group/sort toolbar, but no data columns at all — only the index column. Eight binding forms all tried, none renders columns:columnscolumnscolumns({field, label})viewNamereference to a saved viewviewreference to a saved view<column>elementscolumnsat all (default-columns expectation)Expected / contrast
The same block in a
kind: 'react'page works fully:<ListView columns={['name','stage','amount','close_date']}>renders all four columns (Opportunity Name / Stage / Amount / Close Date). So the data path and the block itself are fine — the html-tier attribute → prop binding forcolumnsappears to be dropped.Impact
Any html-tier page (the "parse, never execute" tier meant for AI-drafted/unreviewed pages) cannot show a usable data table — rows without columns. Not a P0 for us (we re-scoped the demo page), but it undercuts the html tier's headline use case of safely accepting AI-authored pages that include data blocks.