Skip to content

fix(app-shell): the object page renders a stored view's judged legacy options bag, as the interface page does (objectui#10380) - #11571

Merged
objectstack-fleet[bot] merged 5 commits into
mainfrom
claude/issue-10380-interface-options-align
Oct 3, 2026
Merged

objectstack-fleet[bot] merged 5 commits into
mainfrom
claude/issue-10380-interface-options-align

Conversation

@objectstack-fleet

Copy link
Copy Markdown
Contributor

Fixes #10380

Clause-②: no. No published schema, type, input or accept set moves. @objectstack/spec 17.6.0 already declares and judges the list overlay's legacy options bag (ListViewOverlayOptionsSchema), and this change makes the object page render what that door accepts, the way the interface page already does. The one new export, storedLegacyOptions in app-shell's ObjectView module, is a helper exported for its pin, like its siblings kanbanViewOptions and timelineViewOptions.

What was wrong

The flattened list overlay in @objectstack/spec 17.6.0 declares a legacy options bag. The view write door judges each options.KIND block key by key with that kind's own block schema. It refuses an out-of-contract key by name and stores what it accepts. The spec describes the bag as an underlay: the top-level KIND block "wins per key where both set one".

InterfaceListPage forwarded a stored row's bag to ListView, and ObjectView dropped it. So one stored row handed the renderer two different configs. Measured on origin/main ab18797, with rows the 17.6.0 door accepts:

  • a timeline was grouped by region on the interface page and ungrouped on the object page (options.timeline.groupByField);
  • a timeline item or kanban card was titled by region on one page and by name on the other (options.timeline.titleField, options.kanban.titleField);
  • a map had a locationField binding on the interface page and none on the object page (options.map).

Ruling A (5824043998) keeps the interface page's forward ("what passes the door is legal"). The seat's answer 5971906253 directs the object page to honour the bag too, and to reuse ListView's existing per-key merge, with no second merge in app-shell.

What changed

  • ObjectView (app-shell). A new helper, storedLegacyOptions(viewDef), returns the stored row's bag, or {} when the row has no bag or the bag is not an object. The relay then:
    • forwards the bag in options. For each kind the bag carries, the bag's block replaces this page's synthesized block (kanbanViewOptions and its siblings). This is the rule InterfaceListPage applies to its mapCfg (view.options.map ?? derived). A synthesized block stands in only for a kind the bag does not carry, so a row with no bag is relayed exactly as before;
    • forwards the view's own top-level block for each kind the bag carries, at the top level, as InterfaceListPage does. ListView's existing per-key merge ({ ...options.KIND, ...KIND } in each render branch) then lays the declared block over the bag. That is the spec's precedence, and no merge is written in app-shell.
  • InterfaceListPage (app-shell). A default binding the page derives from the object (defaultKanbanFromObject, defaultCalendarFromObject, defaultGalleryFromObject, defaultGanttFromObject) no longer fills a kind the row's bag carries. Before this change, the derived block sat at the top level and outranked the row's own bag declaration on every key it set. The object page, which derives nothing, therefore rendered such a row differently. This is the rule mapCfg already follows, extended to the other derived kinds. The forward of options is unchanged (ruling A), and so is the options.map legacy path and its CONTROL pin.
  • The relay census (ObjectView.relayRungCensus-7559.test.ts). The eight per-kind blocks now have a conditional top-level rung that reads viewDef, so the census counts them as relayed. It requires their relayed-nested ledger rows to go ("an absence that came back is not an absence"), and they are replaced by a comment that says why. Their nested options.KIND paths are still written for every row, and are still asserted by name in the census's derivation checks.
  • Changeset: @object-ui/app-shell patch.

What an existing row that still carries options does

Both pages forward the stored bag in the same way, including a key the 17.6.0 door now refuses (for example options.timeline.metaFields). The renderers ignore the retired keys: ObjectTimeline's chip list has been the constant status / priority pair since the metaFields retirement (objectui#10222), and ListView strips the stray kanban groupBy and the calendar dateField / endField. The row is served as stored until its next save, which the door refuses by name. No migration is done, per the maintainer's 「20051 不考虑现有的数据」.

Tests

New pin: ObjectView.storedOptionsBag-10380.test.tsx. Each case renders one stored flat overlay row through both pages, captures the schema each page hands ListView, mounts the REAL ListView on it with a spy renderer for the kind, and compares what the renderer receives. The cases are:

  • four rows carrying a bag (options.timeline.titleField; options.map; options.timeline.groupByField under a declared timeline; options.kanban.titleField under a declared kanban);
  • a CONTROL row with no bag;
  • two collision rows where the top-level block must win per key on both pages (the timeline titleField; the kanban lane);
  • a unit case for storedLegacyOptions.

Every row is one the 17.6.0 door accepts, judged with the spec's own ViewMetadataSchema.safeParse and diagnoseViewMetadata from the installed @objectstack/spec 17.6.0: success=true, branch=listOverlay, with options kept in the parse.

The direction of each run was written before it ran. Each run used repo-root pnpm exec vitest run FILE, under os-verify-lock:

  • Red on origin/main first. The fix was committed (4d0668d), then ObjectView.tsx and InterfaceListPage.tsx were checked out at ab18797. grep -c legacyOptions read 0 in both files. Result: Tests 6 failed | 2 passed (8).
    • The four bag rows are RED, as predicted. The control and the timeline collision are GREEN, as predicted. storedLegacyOptions is RED because the export does not exist there.
    • ⚠️ The kanban collision was RED, which was NOT predicted. Its lane agreed (region on both pages). It failed on the card title: the object page floored titleField: 'name' and the interface page sent none for a row whose bag carries a kanban block. The fix removes that difference, because the bag's block replaces the synthesized one.
    • Restored with git checkout HEAD --. The blob hashes matched HEAD and git diff HEAD was empty.
  • Ablation on the fixed tree. The declared block was merged UNDER the bag in app-shell ({ ...viewDef.KIND, ...legacyOptions.KIND } at the top level, for timeline and kanban). That is the second merge, with the wrong precedence, that the direction forbids. The anchors were checked on disk before the run: 1 → 0, and the injected text 0 → 1. Predicted: both collision cases RED. Observed: Tests 3 failed | 5 passed (8), which is both collisions plus the options.timeline.groupByField row. That row turned red because ListView reads groupByField as a flat timeline key off the top-level block only, so the merged block exposed it on the object page alone. Restored and verified the same way.
  • On the final head 44e55cf:
    • pnpm --filter @object-ui/app-shell type-check exit 0. Its tsconfig.test.json covers the new test: it reported a type error there on an earlier commit.
    • pnpm exec vitest run packages/app-shell/src/views/ObjectView packages/app-shell/src/views/InterfaceListPage packages/app-shell/src/views/__tests__/PageView packages/app-shell/src/no-refresh-key-remount.ratchet.test.ts packages/app-shell/src/views/view-filter-fold.ratchet.test.ts gives Test Files 55 passed (55) and Tests 504 passed (504). This covers every ObjectView.* and InterfaceListPage.* suite, including the options.map CONTROL pin, the relay census, titleFieldConvergence, the calendar / gallery / gantt / timeline binding pins and hostRerenderRefetch-10046.
    • NOT MEASURED: the full app-shell suite (979 test files). The run was narrowed to the suites that render or read the two edited modules, and CI runs the rest.
  • Build: turbo run build --filter='@object-ui/app-shell^...' --concurrency=2 gave 28 of 28 tasks successful.
  • Lint, narrowed and stated as such:
    • eslint --no-inline-config on the four touched .ts/.tsx files gives files=4, 0 errors.
    • The population is eslint.config.js's **/*.{ts,tsx} block. It uses tseslint.configs.recommended with no parserOptions.project and no projectService, so linting is not type-aware and this diff cannot move a verdict on an untouched file.
    • Warnings against ab18797, base → head: ObjectView.tsx 171 → 173 (one any in the helper's return type, and the react-refresh/only-export-components warning every sibling exported helper carries), InterfaceListPage.tsx 41 → 41, the census 0 → 0. The new test has 19 no-explicit-any warnings, in line with its siblings. No --max-warnings is set in this repo.
  • Gates on 44e55cf, all exit 0:
    • pnpm check:control-bytes, pnpm check:new-line-citations (0 new citations), pnpm check:pending-changeset-literals, pnpm check:spec-symbols, pnpm check:self-import and pnpm check:phantom-deps;
    • pnpm check:changeset-claims: report-only. It names 7070-no-invented-gantt-date-fields.md and 7218-rowcolor-host-relay.md. Both paragraphs were re-read and both are still true;
    • node scripts/check-changeset-presence.mjs, check-changeset-no-major.mjs, check-test-path-roots.mjs, check-vi-mock-specifiers.mjs, check-vi-mock-inherit.mjs and check-vi-mock-override-shape.mjs.

Acceptance notes

  • Residual, the chart view's own route. A type: 'chart' row whose chart block lives ONLY in the bag passes the 17.6.0 door. The object page renders chart views through its dedicated ObjectChart route, which reads viewDef.chart alone and never reaches ListView. So that row still renders the bag's chart on the interface page and the default binding on the object page. Aligning it means either a second chart resolution in app-shell (the chart || options.chart rule of ListView's resolveListChartBinding), which the direction forbids, or exporting that resolver from @object-ui/plugin-list, which adds a published name. That is left to the seat. Evidence: the door acceptance was measured, and the route was read from source and not rendered.
  • Pre-existing, not this card: the interface page drops a declared top-level tree / chart block. InterfaceListPage's schema literal forwards kanban, calendar, gallery, timeline, gantt and map, and has no tree or chart rung. tree and chart are allowed visualizations, and CreateViewDialog writes both blocks on the views it creates. A view's tree.parentField or chart binding therefore reaches ListView on the object page and not on the interface page. This is reported for the seat and not fixed here, because it is independent of the bag and would change the interface page for rows without one. Read from source.
  • Pre-existing, posture: page-derived defaults. An interface page still derives a binding for a whitelisted kind that the row declares nowhere, and the object page never invents one (objectui#3129, objectui#7029). That is a deliberate difference between the pages and is untouched. This change only stops the derivation from outranking a bag declaration. The kanban titleField: 'name' floor of kanbanViewOptions likewise still applies to rows without a bag.
  • Legacy rows (the dev report's out-of-scope finding). A stored row whose bag holds a key the door now refuses is served as stored until its next console save (rename or pin, through data-objectstack's updateView, which merges the current row). The door then refuses that save with a 422 that names the key. This is landed objectstack behaviour (fix(metadata-protocol,spec)!: a saved view stores the parsed value of every key its body carried, and a ViewItem record's top-level options is refused by name (stage iv of #20051) objectstack#20868, 9905e61c). Noted here and not filed, per the seat's answer.
  • Docs: none touched. No page under content/docs/ or the app-shell README describes the bag or the interface page's derived defaults. The two pages that mention a listViews entry's options bag describe the authored object schema, where the bag is still refused, and they stay true.

Session: https://claude.ai/code/session_01FjqrwXPfSMkSfkKYDSRkN2 (dispatched dev of domain:ui seat 1, claim 5971770388, as amended by 5971906253).


Generated by Claude Code

claude added 5 commits October 3, 2026 18:10
… options bag, as the interface page does

The flattened list overlay of @objectstack/spec 17.6.0 declares a legacy
`options` bag, judges each `options.KIND` block key by key and stores it.
InterfaceListPage forwarded the bag to ListView and ObjectView dropped it,
so one stored row handed the renderer two different configs.

ObjectView now forwards the bag. For each kind the bag carries, the bag's
block replaces the page's synthesized block (the mapCfg rule) and the
view's own top-level block goes out at the top level, so ListView's
existing per-key merge lays it over the bag. InterfaceListPage's derived
defaults no longer fill a kind the bag carries, the rule mapCfg already
follows, so a derived guess no longer outranks the row's declaration.

Claude-Session: https://claude.ai/code/session_01FjqrwXPfSMkSfkKYDSRkN2
Co-authored-by: Claude <noreply@anthropic.com>
…tions bag parity pins

Claude-Session: https://claude.ai/code/session_01FjqrwXPfSMkSfkKYDSRkN2
Co-authored-by: Claude <noreply@anthropic.com>
…ns so tsc takes the relay's call

Claude-Session: https://claude.ai/code/session_01FjqrwXPfSMkSfkKYDSRkN2
Co-authored-by: Claude <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

changeset-claim-re-read

⚠️ 2 pending changeset(s) describe a file this change touches

Their bodies publish verbatim into the CHANGELOG at the next release, so this is a request to re-read them against your diff — addressed here because you are the one seat that can answer it without re-deriving anything.

⛔ Nothing here blocks, and nothing here is a verdict on your change. This gate exits 0, is not a required context, and judges name resolution, never meaning: it asked whether a pending body names a file you touched. "Is this sentence still true?" is the one question it will not answer, and the one you are being asked to answer.

.changeset/7070-no-invented-gantt-date-fields.md

  • names app-shell/src/views/ObjectView.tsx → packages/app-shell/src/views/ObjectView.tsx — edited by this change

    • app-shell/src/views/ObjectView.tsx — the console object page. The inline branch becomes ganttViewOptions, the sibling of calendarViewOptions and timelineViewOptions: the declared block spread whole, title floored at 'name', no date field invented. - plugin-list/src/ListView.tsx — the render branch AND the capability gate. - plugin-view/src/ObjectView.tsx — generateViewSchema, the authored object-view element route, which bypasses ListView entirely.

.changeset/7218-rowcolor-host-relay.md

  • names InterfaceListPage.tsx → packages/app-shell/src/views/InterfaceListPage.tsx — edited by this change

    This is a relay, not a new surface. The interface route (InterfaceListPage.tsx) has shipped rowColor: view.rowColor next to grouping and pagination since ADR-0047, into a schema typed ListViewSchema, with no fence of any kind — so the key was already author-reachable and already had a delivery path; two of three hosts simply did not use it. The legacy shorthand for the same feature (bare color) already had a rung in both literals; only the spec-canonical spelling was missing.

Read the paragraph, not the line: both false halves of the objectui#8617 claim sat in one paragraph, and correcting either alone would have left it asserting the same wrong thing.

If a claim did go false, correct the body. That is precedented and prose-only, frontmatter untouched; check-changeset-overwrite.mjs will report the correction as its own case 2 ("correcting a declaration on purpose … legitimate"), which is the intended shape — one gate asks for the read, the other records the write.

Not covered, stated so nobody reads this as more: a born-false claim that spells no line address at all (objectui#9495 coordinated one by ORDINAL — "a grep finds that member first" — and deciding that means reading what the sentence means), a claim spelled as a symbol or a package rather than a backticked file name, and a file named ambiguously.

Compared the checked-out tree with ab1879721 (merge-base with origin/main): 4 file(s) changed outside .changeset/, read against 2091 pending declaration(s) that publish a body (2726 pending in total). · run

@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

✅ Console Performance Budget

Metric Value Budget
Eager closure (gzip, 330 chunks) 3310.7 KB 3330.4 KB
Main entry chunk (gzip) 151.3 KB 350 KB
Entry file index-D5jRmG5V.js —
Status PASS —

The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it.


📦 Bundle Size Report

Package Size Gzipped
app-shell (consoleActionDispatch.js) 0.20KB 0.19KB
app-shell (index.js) 17.22KB 6.37KB
app-shell (runtime-config.js) 20.68KB 7.36KB
app-shell (types.js) 0.01KB 0.04KB
app-shell (urlParams.js) 10.11KB 3.87KB
auth (ActiveOrganizationStorage.js) 27.95KB 10.04KB
auth (AuthContext.js) 0.31KB 0.24KB
auth (AuthGuard.js) 2.07KB 1.00KB
auth (AuthProvider.js) 40.22KB 10.61KB
auth (AuthShell.js) 3.49KB 1.40KB
auth (ForgotPasswordForm.js) 12.21KB 3.45KB
auth (LoginForm.js) 18.17KB 5.40KB
auth (PreviewBanner.js) 0.90KB 0.50KB
auth (RegisterForm.js) 6.72KB 2.24KB
auth (SocialSignInButtons.js) 9.70KB 3.93KB
auth (UserMenu.js) 3.39KB 1.21KB
auth (auth-gate-events.js) 1.29KB 0.66KB
auth (authStyles.js) 5.04KB 1.72KB
auth (createAuthClient.js) 40.70KB 10.94KB
auth (createAuthenticatedFetch.js) 8.54KB 3.46KB
auth (index.js) 3.63KB 1.64KB
auth (invitation-status.js) 1.22KB 0.70KB
auth (org-roles.js) 6.66KB 2.78KB
auth (phone-identifier.js) 1.11KB 0.66KB
auth (types.js) 0.59KB 0.35KB
auth (useAuth.js) 5.30KB 1.02KB
auth (useWorkspaceAdminStatus.js) 11.08KB 4.58KB
collaboration (CommentThread.js) 27.11KB 7.97KB
collaboration (LiveCursors.js) 3.17KB 1.27KB
collaboration (PresenceAvatars.js) 6.28KB 2.60KB
collaboration (PresenceProvider.js) 2.79KB 1.13KB
collaboration (index.js) 1.68KB 0.73KB
collaboration (useCollaborationTranslation.js) 6.50KB 2.52KB
collaboration (useCommentSearch.js) 1.98KB 0.88KB
collaboration (useConflictResolution.js) 7.75KB 1.86KB
collaboration (useMentionNotifications.js) 1.81KB 0.68KB
collaboration (usePresence.js) 6.33KB 1.84KB
collaboration (useRealtimeSubscription.js) 7.91KB 2.01KB
components (index.js) 572.97KB 137.34KB
core (index.js) 10.00KB 3.96KB
create-plugin (index.js) 27.94KB 9.51KB
data-objectstack (index.js) 232.57KB 64.51KB
fields (index.js) 261.62KB 66.20KB
i18n (LocalizationContext.js) 1.76KB 0.96KB
i18n (builtinAggregateLabels.js) 0.86KB 0.49KB
i18n (currency.js) 2.59KB 1.22KB
i18n (fallbackInterpolation.js) 6.25KB 2.77KB
i18n (i18n.js) 8.87KB 3.64KB
i18n (index.js) 5.24KB 2.27KB
i18n (pickLocalized.js) 9.86KB 3.95KB
i18n (provider.js) 39.35KB 12.88KB
i18n (translateFn.js) 0.20KB 0.18KB
i18n (useDisplayLocale.js) 3.52KB 1.76KB
i18n (useObjectLabel.js) 35.66KB 9.49KB
i18n (useSafeTranslation.js) 7.14KB 2.92KB
layout (index.js) 39.47KB 11.25KB
mobile (MobileProvider.js) 0.92KB 0.49KB
mobile (ResponsiveContainer.js) 0.94KB 0.38KB
mobile (breakpoints.js) 1.51KB 0.70KB
mobile (createOfflineDataSource.js) 5.61KB 1.75KB
mobile (index.js) 1.99KB 0.87KB
mobile (offlineQueue.js) 3.91KB 1.35KB
mobile (pwa.js) 0.97KB 0.49KB
mobile (serviceWorker.js) 1.48KB 0.62KB
mobile (serviceWorkerSource.js) 3.41KB 1.48KB
mobile (useBreakpoint.js) 1.54KB 0.65KB
mobile (useGesture.js) 6.96KB 1.98KB
mobile (useOfflineSync.js) 1.99KB 0.72KB
mobile (usePullToRefresh.js) 6.62KB 2.45KB
mobile (useResponsive.js) 0.72KB 0.42KB
mobile (useSpecGesture.js) 5.52KB 2.10KB
mobile (useTouchTarget.js) 1.01KB 0.54KB
permissions (MePermissionsProvider.js) 13.86KB 5.00KB
permissions (PermissionContext.js) 0.31KB 0.25KB
permissions (PermissionGuard.js) 0.89KB 0.45KB
permissions (PermissionProvider.js) 6.52KB 2.26KB
permissions (discardProofCache.js) 1.04KB 0.55KB
permissions (evaluator.js) 8.33KB 3.07KB
permissions (index.js) 0.93KB 0.41KB
permissions (store.js) 0.91KB 0.42KB
permissions (useFieldPermissions.js) 1.28KB 0.53KB
permissions (usePermissions.js) 4.83KB 2.27KB
plugin-ai (index.js) 16.04KB 3.92KB
plugin-calendar (index.js) 53.17KB 15.46KB
plugin-charts (index.js) 83.60KB 22.89KB
plugin-chatbot (index.js) 198.22KB 46.97KB
plugin-dashboard (index.js) 142.26KB 38.44KB
plugin-designer (index.js) 231.28KB 48.76KB
plugin-detail (index.js) 245.60KB 64.57KB
plugin-editor (index.js) 2.23KB 1.05KB
plugin-form (index.js) 175.44KB 45.28KB
plugin-gantt (index.js) 179.16KB 45.06KB
plugin-grid (index.js) 235.02KB 64.63KB
plugin-kanban (index.js) 49.59KB 15.58KB
plugin-list (index.js) 116.46KB 28.93KB
plugin-map (index.js) 25.60KB 8.62KB
plugin-markdown (index.js) 13.88KB 4.80KB
plugin-report (index.js) 44.12KB 12.29KB
plugin-timeline (index.js) 38.80KB 11.71KB
plugin-tree (index.js) 14.51KB 5.15KB
plugin-view (index.js) 90.23KB 22.73KB
providers (DataSourceProvider.js) 0.75KB 0.39KB
providers (MetadataProvider.js) 1.37KB 0.59KB
providers (ThemeProvider.js) 1.90KB 0.85KB
providers (UploadProvider.js) 11.81KB 3.58KB
providers (index.js) 0.45KB 0.23KB
providers (types.js) 0.01KB 0.04KB
react-runtime (index.js) 5.62KB 2.34KB
react (LazyPluginLoader.js) 4.47KB 1.63KB
react (SchemaRenderer.js) 120.63KB 39.56KB
react (data-invalidation.js) 5.05KB 2.08KB
react (index.js) 4.50KB 2.06KB
react (schema-input.js) 4.25KB 2.04KB
react (spec-input.js) 0.20KB 0.18KB
sdui-parser (body-dialect.js) 4.50KB 1.99KB
sdui-parser (codegen.js) 9.45KB 3.76KB
sdui-parser (dashboard-widget-options.js) 3.08KB 1.30KB
sdui-parser (index.js) 6.06KB 2.68KB
sdui-parser (input-type.js) 2.84KB 1.40KB
sdui-parser (parse.js) 25.28KB 7.80KB
sdui-parser (provenance.js) 3.84KB 1.90KB
sdui-parser (types.js) 0.28KB 0.23KB
sdui-parser (validate.js) 21.42KB 7.05KB
types (ai.js) 4.39KB 2.17KB
types (api-types.js) 0.20KB 0.18KB
types (app.js) 4.12KB 1.61KB
types (authoring-nodes.js) 0.20KB 0.19KB
types (base.js) 0.20KB 0.18KB
types (blocks.js) 0.20KB 0.18KB
types (cloud.js) 0.20KB 0.18KB
types (complex.js) 4.16KB 1.96KB
types (crud.js) 0.20KB 0.18KB
types (dashboard-filter-alias.js) 6.23KB 2.74KB
types (dashboard-widget-layout.js) 2.06KB 0.96KB
types (data-display.js) 3.75KB 1.85KB
types (data-protocol.js) 0.20KB 0.19KB
types (data.js) 0.20KB 0.18KB
types (designer.js) 1.85KB 0.85KB
types (disclosure.js) 0.20KB 0.18KB
types (error-code.js) 1.54KB 0.88KB
types (expression.js) 0.20KB 0.18KB
types (feedback.js) 0.20KB 0.18KB
types (field-types.js) 0.20KB 0.18KB
types (form.js) 0.20KB 0.18KB
types (http-inflight.js) 8.87KB 3.73KB
types (http-retry.js) 4.32KB 2.02KB
types (icon-key-migration.js) 4.26KB 1.63KB
types (index.js) 5.07KB 2.39KB
types (layout.js) 0.20KB 0.18KB
types (managed-by.js) 0.19KB 0.18KB
types (mobile.js) 5.00KB 2.39KB
types (navigation.js) 0.20KB 0.18KB
types (objectql.js) 0.20KB 0.18KB
types (overlay.js) 0.20KB 0.18KB
types (permissions.js) 2.52KB 1.31KB
types (plugin-scope.js) 0.20KB 0.18KB
types (record-components.js) 0.20KB 0.19KB
types (record-semantics.js) 1.28KB 0.67KB
types (registry.js) 0.20KB 0.18KB
types (reports.js) 0.20KB 0.18KB
types (select-option.js) 0.20KB 0.19KB
types (spec-report.js) 4.99KB 1.96KB
types (spec-ui-namespace.js) 0.20KB 0.19KB
types (strict-authoring-face.js) 19.93KB 7.25KB
types (system-fields.js) 3.33KB 1.54KB
types (theme.js) 6.28KB 2.87KB
types (ui-action.js) 8.11KB 3.32KB
types (views.js) 0.20KB 0.18KB
types (widget.js) 0.20KB 0.18KB

Size Limits

  • ✅ Core packages should be < 50KB gzipped
  • ✅ Component packages should be < 100KB gzipped
  • ⚠️ Plugin packages should be < 150KB gzipped

@objectstack-fleet
objectstack-fleet Bot marked this pull request as ready for review October 3, 2026 18:48
@objectstack-fleet
objectstack-fleet Bot enabled auto-merge October 3, 2026 18:48
@objectstack-fleet
objectstack-fleet Bot added this pull request to the merge queue Oct 3, 2026
Merged via the queue into main with commit 0685646 Oct 3, 2026
45 checks passed
@objectstack-fleet
objectstack-fleet Bot deleted the claude/issue-10380-interface-options-align branch October 3, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

2 participants