Issues

docs(guide): `objectos-integration.mdx:280` authors `object-grid.filter` as an `and:`-keyed object of `{ field, operator, value }` entries — a shape no reader lowers (`toFilterNode` emits `['and', '=', [...]]`)

#7713

· claude opened

on Sep 5, 2026

plugin-calendar: `getCalendarConfig` reads `schema.filter.calendar` as the calendar configuration container — the `filter.map` defect #4034 closed, still live on the calendar (`ObjectCalendar.tsx:145`)

#7711

· claude opened

on Sep 5, 2026

plugin-kanban / plugin-calendar: the registrations declare no `filter` input while both renderers read `schema.filter` and the spec declares it — the html tier reports `unknown-prop` on a spec-declared key (objectui#6678 class)

#7712

· claude opened

on Sep 5, 2026

finding(i18n): the maker's EDIT-mode chip still offers 「加一个自动化 —— 审批、状态流转或通知」, which ADR-0112 v1 cannot build

finding

#7709

· hotlong opened

on Sep 5, 2026

finding(plugin-chatbot): `chatbot-floating` spreads the whole authored node raw and LAST onto its panel — three undeclared keys are live, the authored `messages` seed overrides the runtime messages (a sent message never renders), and node keys land as DOM attributes

#7708

· os-sam opened

on Sep 5, 2026

FlowRunner: render a flow that ended with `outcome: 'refused'` as a Close-only notice with no "completed" toast (lane 3 of objectstack#14945 ruling 2′)

#7707

· claude opened

on Sep 5, 2026

finding(types): two arity conventions for runtime handler slots - 11 slots take no event, 8 take one, and the arity-0 form cannot express preventDefault

#7706

· claude opened

on Sep 5, 2026

finding(types): `SchemaRegistry` / `ComponentType` omit `chatbot-enhanced` and `chatbot-floating` — two registered keys the layer can now name

#7704

· os-sam opened

on Sep 5, 2026

finding(types/plugin-chatbot): six `ChatbotSchema` keys are declared and read by no registration — `loading`, `showAvatars`, `userAvatar`, `assistantAvatar`, `markdown`, `height`

#7703

· os-sam opened

on Sep 5, 2026

finding(cli): union-arm-diagnostics states 108 AnyComponentSchema arm names and 14 union members as measured facts; the tree reads 105 and 13

#7702

· claude opened

on Sep 5, 2026

[finding] fileValueForSubmit still submits the legacy inline blob when the upload adapter surfaces no fileId — the one client path still producing the pre-D3 stored shape

#7699

· claude opened

on Sep 5, 2026

finding(plugin-charts): series-level `opacity` and `dashArray` are honoured only on a `variant: 'comparison'` series — read and unused on a primary series, while the spec declares them as unconditional overrides

#7698

· claude opened

on Sep 5, 2026

Navigation Menu

Uh oh!

All issues

docs(guide): `objectos-integration.mdx:280` authors `object-grid.filter` as an `and:`-keyed object of `{ field, operator, value }` entries — a shape no reader lowers (`toFilterNode` emits `['and', '=', [...]]`)

plugin-calendar: `getCalendarConfig` reads `schema.filter.calendar` as the calendar configuration container — the `filter.map` defect #4034 closed, still live on the calendar (`ObjectCalendar.tsx:145`)

plugin-kanban / plugin-calendar: the registrations declare no `filter` input while both renderers read `schema.filter` and the spec declares it — the html tier reports `unknown-prop` on a spec-declared key (objectui#6678 class)

finding(i18n): the maker's EDIT-mode chip still offers 「加一个自动化 —— 审批、状态流转或通知」, which ADR-0112 v1 cannot build

finding(plugin-chatbot): `chatbot-floating` spreads the whole authored node raw and LAST onto its panel — three undeclared keys are live, the authored `messages` seed overrides the runtime messages (a sent message never renders), and node keys land as DOM attributes

FlowRunner: render a flow that ended with `outcome: 'refused'` as a Close-only notice with no "completed" toast (lane 3 of objectstack#14945 ruling 2′)

finding(types): two arity conventions for runtime handler slots - 11 slots take no event, 8 take one, and the arity-0 form cannot express preventDefault

finding(types): `SchemaRegistry` / `ComponentType` omit `chatbot-enhanced` and `chatbot-floating` — two registered keys the layer can now name

finding(types/plugin-chatbot): six `ChatbotSchema` keys are declared and read by no registration — `loading`, `showAvatars`, `userAvatar`, `assistantAvatar`, `markdown`, `height`

finding(cli): union-arm-diagnostics states 108 AnyComponentSchema arm names and 14 union members as measured facts; the tree reads 105 and 13

[finding] fileValueForSubmit still submits the legacy inline blob when the upload adapter surfaces no fileId — the one client path still producing the pre-D3 stored shape

finding(plugin-charts): series-level `opacity` and `dashArray` are honoured only on a `variant: 'comparison'` series — read and unused on a primary series, while the spec declares them as unconditional overrides

Uh oh!

Search results