Skip to content

Commit ba1f164

Browse files
fix(app-shell): interface list toolbar honours the userActions spec defaults — Filter, Row height, Group and Hide Fields are on unless written false (#29299)
<!-- claude-projects-attribution: {"github_login":"zhuangjianguo"} --> _Requested by **Steedos** · [project thread](https://claude.ai/code/project/chan_018ETKaNwMZCNRYD7D8Q9Ubb?thread=cmsg_018ETKaNwMZCNRYD7D8Q9UbbK4zrqkvfgzpmvBDm7Q5uxL)_ Fixes #29144 Clause-②: no Metadata-protocol: semantic Skills-docs: none — `git grep -n "userActions" skills/` names no interface-page toolbar default; the skills describe neither the old closed reading nor the new one ## 维护者速读 - **改了什么**:界面页(interface page)列表工具栏的「筛选 / 行高 / 分组 / 隐藏字段」四个开关,改为与列表视图同一份 `userActions` 规范默认值:不写即开启,写 `false` 才关闭;「行着色」仍需显式开启。ADR-0047 同步加一段修订说明。 - **为什么改**:规范把这四项默认设为开,但界面页只认显式 `true`,同一张页面经过解析就有按钮、未解析(无 userActions 块或 Studio 存储行)就没有,两种工具栏全凭页面进入控制台的路径决定。 - **风险与回滚**:没写 userActions 块的界面页、以及未解析存储的页面,会多出这四个按钮;代码包里已声明 userActions 块的示例页(showcase 11 张、HotCRM 1 张)解析后本来就有分组和隐藏字段,无变化。回滚即还原 `InterfaceListPage.tsx` 一处映射。 - **先看**:`ui/packages/app-shell/src/views/InterfaceListPage.tsx`(userActions 映射那段);`docs/adr/0047-object-ui-run-modes.md`(修订横幅);`.changeset/29144-interface-toolbar-spec-defaults.md`。 - **两分钟验证**:`cd ui && pnpm exec vitest run packages/app-shell/src/views/InterfaceListPage.userActionsSpecDefaults.test.tsx`,预期 17 个用例全绿。 - **需要你做的**:本 PR 触及 `docs/adr/**`(Tier H),待席位 ACCEPT 后请审阅并批准合并。 ## What changes - `InterfaceListPage` reads `filter`, `rowHeight`, `group` and `hideFields` from the page's `interfaceConfig.userActions` as `!== false`, the published default of `UserActionsConfigSchema` (the schema a list view's `userActions` uses too). `search` and `sort` already read this way. `rowColor`, off by default in the spec, stays `=== true`. Export stays off. - A page with no `userActions` block, a stored page that was never parsed, and a parsed block that omits a key now draw the same toolbar. Before, only the parsed block drew the four controls, because the parse had written the default `true` that `=== true` was waiting for. - ADR-0047 gets a dated amendment banner and status note under the maintainer's ruling (#29144 comment 6574404727, batch #455, letter A): the toolbar toggles take the shared defaults; §3.4's closed rows (quick filters, visualization lock, no user-created views, session filter state) and the export lock stand. `docs/adr/README.md` is regenerated by `pnpm adr:index`. - The sentence "an interface page keeps its own closed-by-default toolbar" is corrected in three places: the `list-view-hide-fields-default-on` semantic entry, the default-change ledger reason (`packages/spec/scripts/lib/default-changes.ts`) and the still-pending changeset `.changeset/28912-hide-fields-default-on.md` (one bullet), which would otherwise publish the now-false sentence. ### Reach (measured at 49aba82) | Pages | userActions block | Today | After | |---|---|---|---| | showcase `active-projects`, `review-queue`, `task-triage`, `task-workbench` and the seven `task-visualizations` pages (11 pages); HotCRM `account_workbench` | declared, omits `group` / `hideFields` | parsed by `defineStack`: Group and Hide Fields already drawn | unchanged | | any page with no block; any stored page never parsed (Studio drafts and rows) | absent or unparsed | none of the four drawn | Filter, Row height, Group, Hide Fields drawn unless written `false` | The parse reading: `PageSchema.parse` of a block `{ sort, search, filter: false, rowHeight: false, addRecordForm: false }` yields `group: true` and `hideFields: true`; a page with no block parses with none. ## Tests - New `InterfaceListPage.userActionsSpecDefaults.test.tsx` (17 cases): no block, an unparsed `{}` and a parsed `{}` (through the real `PageSchema`) compose the same spec-default toolbar; a curated block composes the same toolbar parsed or unparsed; an explicit `false` withholds each of the four alone; an explicit `true` keeps each; for four blocks the page draws exactly what a list view parses the same block to (`UserActionsConfigSchema.parse`); `rowColor` stays opt-in. - A list view is unchanged: `ListView.test.tsx` (its `hideFields` default-on, explicit `false` and `group: false` cases) runs green beside the page tests. - `InterfaceListPage.relayCensus-11572.test.ts`: the `userActions` and `compactToolbar` reasons no longer say "closed by default". - Ablation: restoring `hideFields: userActions.hideFields === true` (through `scripts/ablation-replace.mjs`, anchor 1 → 0, replacement 0 → 1) turns 8 of 17 cases red on the final head (the parsed-`{}` case stays green under the ablation, which is the defect: only a parse made the old read draw the control); the restored blob equals HEAD and `git diff HEAD` is empty. ## Acceptance notes - A list view's toolbar is unchanged: `ListView` already reads these four as `!== false`; this diff does not touch `@object-ui/plugin-list`. - **`check-empty-changeset` stays red on purpose.** This PR edits `.changeset/28912-hide-fields-default-on.md`, a pending release note it did not add. That is the gate's DELIBERATE CORRECTION class: the note's interface-page bullet said the page keeps a closed-by-default toolbar, which this change makes false, so restoring it would publish a false sentence. The one bullet now says the page reads the same default and `hideFields: false` withholds the control. The correction is named in the claim amendment (#29144 comment 6574419950) under the maintainer's ruling; the maintainer confirms it with the Tier H approval. ## Verification All readings on head `05795338` (branch merged with `origin/main` at `eb14f7ad`). Head `899749f6` only raises the changeset's `@objectstack/spec` grade from `patch` to `minor` (the level axis of `check-changeset-no-major`: a `semantic` change takes `minor` on a moved, published package); on it the changeset gates were rerun: `check-changeset-no-major` 0, `check:changeset-gate-self-tests` 0, `check-adr-0087-registration` 0, `check:pm-changeset-deadline-census` 0, `check:doc-authoring` 0, `check:issue-citations` 0, `check:nul-bytes` 0, `check-empty-changeset` 1 (as above). <details><summary>Tests (locked, two vitest workers)</summary> - `cd ui && pnpm exec vitest run` over the 11 `InterfaceListPage.*` test files plus `plugin-list/src/__tests__/ListView.test.tsx`: Test Files 12 passed, Tests 249 passed. - `pnpm exec turbo run type-check --filter=@object-ui/app-shell`: 65 of 65 tasks green. - `pnpm --filter @objectstack/spec check:generated`: all 14 generated artifacts up to date. - `pnpm --dir ui exec vitest run scripts/`: Test Files 169 passed, 2 skipped; Tests 4900 passed. - Ablation (`scripts/ablation-replace.mjs`, hideFields back to `=== true`): Tests 8 failed, 9 passed (17); restored, `git diff HEAD` empty. </details> <details><summary>Derived gates (dispatch-gates commands, 91 families)</summary> - 90 run with exit 0; `node scripts/check-empty-changeset.mjs --base origin/main` exit 1, the deliberate correction named under Acceptance notes. - `dispatch-gates --ran`: 91 derived, 91 run, 0 NOT-MEASURED, 0 UNRUN. - Changed lines 275 (+255 / -20), 9 files, under the 3000 human-merge threshold. Tier H by `docs/adr/0047-object-ui-run-modes.md` and `docs/adr/README.md`. </details> --- _Generated by [Claude Code](https://claude.ai/code/session_01QsR2jUidUZdX3neiGCfRHE)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
1 parent cfe5d49 commit ba1f164

9 files changed

Lines changed: 255 additions & 20 deletions

‎.changeset/28912-hide-fields-default-on.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ A declared default moves. A list view whose `userActions` block says nothing abo
1212

1313
- **Before.** `UserActionsConfigSchema.hideFields` defaulted to `false`, and the list renderer drew the control only for an explicit `hideFields: true`. Generated apps and the CRM example never declared it, so their lists had no way to hide a column.
1414
- **Now.** The default is `true`, and the list renderer reads `hideFields !== false`, so the spec default and the renderer agree. A view with no `userActions` block parses with none, and the renderer reads the absent key as the new default.
15-
- **Interface pages.** A page `interfaceConfig.userActions` block that omits the key parses to `true` as well, but an interface page keeps its own closed-by-default toolbar, as it already does for `filter`, `rowHeight` and `group`: it draws the control only for an explicit `hideFields: true`.
15+
- **Interface pages.** A page `interfaceConfig.userActions` block that omits the key parses to `true` as well, and the interface page reads the same default: a page that omits the key, or has no `userActions` block, offers the control, and `hideFields: false` withholds it.
1616
- **Where the choice is kept** does not change. The control only subtracts from the columns the view draws. On a view that declares `columns`, or a saved view, the choice is stored on the reader's own list state and survives a reload for that reader only. On a system view that declares no `columns`, it lasts for the session. It never writes the shared view.
1717
- **To withhold the control**, write `userActions: { hideFields: false }`. Every authored `hideFields` parses exactly as before, and a non-boolean is still refused.
1818
- **Compiled artifacts.** A document that serialised an earlier parse (an `os compile` artifact) carries the old written `false` and keeps withholding the control. Recompile it, or delete the key.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
'@object-ui/app-shell': minor
3+
'@objectstack/spec': minor
4+
---
5+
6+
fix(app-shell): an interface page's list toolbar reads the published `userActions` defaults — Filter, Row height, Group and Hide Fields are on unless the page writes `false`
7+
8+
Clause-②: no
9+
Metadata-protocol: semantic
10+
11+
An interface page's `interfaceConfig.userActions` is the same `UserActionsConfigSchema` a list view uses, and that schema declares `filter`, `rowHeight`, `group` and `hideFields` on by default. The interface list page read those four as `=== true`, so a control appeared only when a parse had already written the default into the block. The same page drew two different toolbars depending on how it reached the console.
12+
13+
- **Before.** A page whose `userActions` block omitted one of the four drew that control only if the page had been parsed (a code package through `defineStack`). A page with no `userActions` block, or a stored page that was never parsed, drew none of the four.
14+
- **Now.** The page reads `filter`, `rowHeight`, `group` and `hideFields` as on unless the block says `false`. A page with no block, an unparsed stored page and a parsed block that omits the key draw the same toolbar: Filter, Row height, Group and Hide Fields appear, beside Search and Sort, which already read this way.
15+
- **Unchanged.** `rowColor` is off by default in the spec and stays opt-in: the page draws it only for `rowColor: true`. Export stays off on an interface page. A list view's toolbar is unchanged.
16+
- **To keep a control closed** on a curated page, write it: `userActions: { filter: false, rowHeight: false, group: false, hideFields: false }`, or any one of them. Code-package pages that declare a `userActions` block already drew Group and Hide Fields after their parse, so they see no change.
17+
- **Wording.** The `list-view-hide-fields-default-on` semantic entry and the default-change ledger no longer say an interface page keeps a closed-by-default toolbar.

‎docs/adr/0047-object-ui-run-modes.md‎

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# ADR-0047: Two run modes for object UI — data views vs interface pages, user filters, and runtime visualization choice
22

3-
**Status**: Accepted (2026-06-12; revised 2026-06-19) — framework scope implemented (`UserFiltersSchema`/`InterfacePageConfigSchema` + the 2026-07-07 object-list narrowing, reference-integrity diagnostics); the PageView render + Studio panel phases live in objectui.
3+
**Status**: Accepted (2026-06-12; revised 2026-06-19; amended 2026-11-02, interface-page toolbar toggles) — framework scope implemented (`UserFiltersSchema`/`InterfacePageConfigSchema` + the 2026-07-07 object-list narrowing, reference-integrity diagnostics); the PageView render + Studio panel phases live in objectui.
44

55
> **Revision (2026-06-19) — the "iron rule" is superseded.** Validating the
66
> Studio config panel against Airtable showed Airtable has no "inherit from a
@@ -10,6 +10,22 @@
1010
> and the page editor edits them in place. `sourceView` is deprecated and kept
1111
> only as a runtime back-compat fallback. TL;DR #2 below no longer holds; the
1212
> rest of the ADR (two run modes, userFilters, visualization whitelist) stands.
13+
14+
> **Amendment (2026-11-02) — an interface page's toolbar toggles take the shared
15+
> `userActions` defaults.** Maintainer ruling of 2026-11-02, objectstack#29144
16+
> comment 6574404727 (batch #455, letter A).
17+
> A page's `interfaceConfig.userActions` is the same `UserActionsConfigSchema` a
18+
> list view uses, and the page reads it with that schema's published defaults:
19+
> `search`, `sort`, `filter`, `rowHeight`, `group` and `hideFields` are on unless
20+
> the page writes `false`, and `rowColor` is off unless it writes `true`. One
21+
> schema, one set of defaults: a page that omits a key, a page with no block and
22+
> a stored page that was never parsed draw the same toolbar. So TL;DR #1's
23+
> "selected user actions" and TL;DR #5's "closed until the author opens it" no
24+
> longer cover these toggles: they are withheld per key, by writing `false`.
25+
> Everything else interface mode keeps closed stands, as §3.4 lays out: no quick
26+
> filters until the author configures `userFilters`, the visualization locked to
27+
> the authored one unless whitelisted, no user-created views, session-scoped
28+
> filter state; and export stays off on the page.
1329
>
1430
> **Amendment (2026-07-07) — `dropdown` user filters are allowed on object list
1531
> views again (framework #2679 / objectui #2338).** The phase-4 rollout had

‎docs/adr/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ A bare `ADR-0006` names the decision; its current text is [0006-project-environm
117117
| [ADR-0044](./0044-approval-send-back-for-revision.md) | Flow-level send-back-for-revision — `revise` branch + typed back-edge re-entry | Accepted — engine + model implemented; designer pending (objectui) (propos… | 2026-06-12 | — | — |
118118
| [ADR-0045](./0045-additive-materialization-and-visibility-gate.md) | Additive materialization with a visibility gate — drafts narrow to mutations | Accepted — 2026-06-12 · Amended 2026-08-09 (#4829, maintainer ruling 2026-… | 2026-06-12 | — | — |
119119
| [ADR-0046](./0046-package-docs-as-metadata.md) | Package documentation as metadata — flat `src/docs/.md` compiled into the manifest | Accepted — 2026-10-28 (ruled on objectstack#26553, ADR batch 2; proposed 2… | 2026-10-28 | — | — |
120-
| [ADR-0047](./0047-object-ui-run-modes.md) | Two run modes for object UI — data views vs interface pages, user filters, and runtime visualization choice | Accepted — 2026-06-12; revised 2026-06-19 — framework scope implemented (`… | 2026-06-12 | — | — |
120+
| [ADR-0047](./0047-object-ui-run-modes.md) | Two run modes for object UI — data views vs interface pages, user filters, and runtime visualization choice | Accepted — 2026-06-12; revised 2026-06-19; amended 2026-11-02, interface-p… | 2026-06-12 | — | — |
121121
| [ADR-0048](./0048-cross-package-metadata-collision.md) | Cross-package metadata collision — package-id identity, namespace install gate, package-scoped resolution | Revised — 2026-06-13 — supersedes the original per-item collision detecti… | 2026-06-13 | — | ADR-0146 |
122122
| [ADR-0049](./0049-no-unenforced-security-properties.md) | Spec must not declare security properties the runtime does not enforce (enforce-or-remove gate) | Accepted — 2026-06-15 — implemented: fail-closed `DESTRUCTIVEOPERATIONS` (… | 2026-06-15 | — | — |
123123
| [ADR-0050](./0050-form-layout-vs-presentation.md) | Form layout vs presentation — split the overloaded `FormView.type` | Proposed — 2026-06-15 · Amended (2026-10-20, letter B′ on #24692, ruling r… | 2026-06-15 | — | — |

‎packages/spec/scripts/lib/default-changes.ts‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -730,9 +730,9 @@ export const DEFAULT_CHANGES_BY_MAJOR: Readonly<Record<number, readonly Declared
730730
+ '`true` where it parsed to `false`, and the console\'s list offers the Hide Fields control. '
731731
+ 'A view with NO `userActions` block parses with none on either side; the list renderer '
732732
+ 'reads an absent key as this default. A page `interfaceConfig.userActions` block parses to '
733-
+ '`true` too, but an interface page keeps its own closed-by-default toolbar (as it already '
734-
+ 'does for `filter`, `rowHeight` and `group`) and still draws the control only for an '
735-
+ 'explicit `hideFields: true`. The accept set does not move: '
733+
+ '`true` too, and an interface page reads the same default: a page whose block omits the '
734+
+ 'key, or that has no block, offers the control, and `hideFields: false` withholds it, as '
735+
+ 'the page also does for `filter`, `rowHeight` and `group`. The accept set does not move: '
736736
+ '`hideFields` is still a boolean, and every authored value parses exactly as before. The '
737737
+ 'control only subtracts from the columns the view draws, and the choice is the reader\'s '
738738
+ 'own: stored on their list state on a view that declares `columns` or a saved view, '

‎packages/spec/src/migrations/entries/semantic/18.list-view-hide-fields-default-on.ts‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,9 @@ export const entry: SemanticMigration = {
3636
+ 'absent key as the spec default. The control only subtracts from the columns the view draws, '
3737
+ 'and the choice is the reader\'s own: stored on their own list state on a view that declares '
3838
+ '`columns` or on a saved view, kept for the session only on a system view that declares no '
39-
+ '`columns`, and never written into the shared view. An interface page keeps its own '
40-
+ 'closed-by-default toolbar and still draws the control only for an explicit `true`. Not '
39+
+ '`columns`, and never written into the shared view. An interface page reads the same '
40+
+ 'default: a page whose `interfaceConfig.userActions` omits the key, or that has no block, '
41+
+ 'offers the control, and `hideFields: false` withholds it. Not '
4142
+ 'losslessly convertible because the question is intent, not text: only the deployment knows '
4243
+ 'which silent lists were relying on fixed columns. The accept set is unchanged — a boolean — '
4344
+ 'and every authored `hideFields` parses exactly as before. A document that serialised an '

‎ui/packages/app-shell/src/views/InterfaceListPage.relayCensus-11572.test.ts‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -499,7 +499,7 @@ const NOT_RELAYED: Record<string, NotRelayed> = {
499499
addRecord: { kind: 'page-owned', from: 'addRecord', reason: "The page config's add-record entry point. The page states its own; the referenced view's would add a button the page author never configured." },
500500
showRecordCount: { kind: 'page-owned', from: 'showRecordCount', reason: "The page config's record-count toggle, page presentation policy; the referenced view's toggle does not stand in for it." },
501501
allowPrinting: { kind: 'page-owned', from: 'allowPrinting', reason: "The page config's \"Allow users to print the page\". It went unwritten until objectui#11572, so the declared toggle drew no print button; the page's value only, like its siblings." },
502-
userActions: { kind: 'page-owned', from: 'userActions', reason: "The page config's toolbar toggles, with interface-mode defaults (closed unless opted in, #2890). The view's toolbar vocabulary is the object page's policy, not this page's." },
502+
userActions: { kind: 'page-owned', from: 'userActions', reason: "The page config's toolbar toggles, read with the published `UserActionsConfigSchema` defaults (a control is withheld by writing `false`; rowColor is opt-in). The view's toolbar vocabulary is the object page's policy, not this page's." },
503503
inlineEdit: { kind: 'page-owned', from: 'userActions', reason: "Read from the page's `userActions.editInline` (default on since objectstack#22605; `editInline: false` opts out). Whether this page's cells are editable is the page author's decision, not the referenced view's." },
504504
navigation: { kind: 'page-prop', from: 'recordAction', prop: 'onRowClick', reason: "The page config's `recordAction` (drawer / page / modal / none) decides how a record opens, wired through `onRowClick` to this page's own overlay. The view's `navigation` would be a second, competing answer." },
505505

@@ -517,7 +517,7 @@ const NOT_RELAYED: Record<string, NotRelayed> = {
517517
// The spec scopes `sourceView` to "columns/filter/sort", and the page config
518518
// declares none of these. Each also has a page-layer reason of its own.
519519
aria: { kind: 'not-inherited', reason: "Accessible naming of the list region. The page owns the region it renders; the referenced view's label would name the region after a view the page only borrows columns from." },
520-
compactToolbar: { kind: 'not-inherited', reason: 'Toolbar layout. The toolbar on this surface is page policy (`userActions`, closed by default), and the page config has no compact-toolbar key to set.' },
520+
compactToolbar: { kind: 'not-inherited', reason: 'Toolbar layout. The toolbar on this surface is page policy (`userActions`), and the page config has no compact-toolbar key to set.' },
521521
conditionalFormatting: { kind: 'not-inherited', reason: "Row styling rules, outside the spec's columns/filter/sort inheritance. ⚠️ `rowColor` IS relayed: a pre-existing relay outside the line, recorded in this file's header and not extended here." },
522522
// `filterableFields` was answered here (`not-inherited`) until objectui#13118:
523523
// the spec retires it (objectstack#24640, ruling C) and `ListView` reads it

‎ui/packages/app-shell/src/views/InterfaceListPage.tsx‎

Lines changed: 20 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,9 @@
1414
* • end users get exactly the `userFilters` the author enabled;
1515
* • the visualization comes from `appearance.allowedVisualizations`
1616
* (a single entry renders no switcher);
17-
* • `userActions` toggles map onto the toolbar — advanced filtering and
18-
* view management are absent by default.
17+
* • `userActions` toggles map onto the toolbar with the published defaults
18+
* of `UserActionsConfigSchema` — an author withholds a control by
19+
* writing `false` for it.
1920
*
2021
* Every member `ListView` reads is either relayed by the `schema` memo below
2122
* or answered as deliberately not relayed, with its reason, in
@@ -576,17 +577,26 @@ export function InterfaceListPage({ page, className, onConfigChange, reserveEdit
576577
// off here and hardcoded on in ObjectDataPage: two surfaces, two opposite
577578
// policies, neither author-controllable. They are author-controllable now.
578579
//
579-
// Interface mode stays closed BY DEFAULT — the advanced filter builder,
580-
// density and the view-management tools are present only when the author
581-
// opted in — but "closed by default" is expressed as a default here, not
582-
// as an unreachable constant.
580+
// Each toggle reads the published default of `UserActionsConfigSchema`,
581+
// the one schema a page's `interfaceConfig.userActions` and a list
582+
// view's `userActions` share: search, sort, filter, rowHeight, group and
583+
// hideFields are on unless the author writes `false`; rowColor is off
584+
// unless the author writes `true`. A page with no `userActions` block, a
585+
// stored page that was never parsed, and a parsed block that omits a key
586+
// therefore draw the same toolbar. Reading the on-by-default four as
587+
// `=== true` drew a control only after a parse had materialised the
588+
// default, so the same page opened with a different toolbar depending
589+
// on how it reached the console. A curated page keeps a control closed
590+
// by writing `false` for it. ADR-0047 as amended 2026-11-02: the rest of
591+
// interface mode (quick filters, the visualization lock, user-created
592+
// views, export) stays closed.
583593
userActions: {
584594
search: userActions.search !== false,
585595
sort: userActions.sort !== false,
586-
filter: userActions.filter === true,
587-
rowHeight: userActions.rowHeight === true,
588-
group: userActions.group === true,
589-
hideFields: userActions.hideFields === true,
596+
filter: userActions.filter !== false,
597+
rowHeight: userActions.rowHeight !== false,
598+
group: userActions.group !== false,
599+
hideFields: userActions.hideFields !== false,
590600
rowColor: userActions.rowColor === true,
591601
},
592602
allowExport: false,

0 commit comments

Comments
 (0)