make-app-actions

Implements Make CanvasTable record selection actions, permission prechecks, and batch editing.

5|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/qfeius/make-platform-skills --skill make-app-actions-qfeius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-app-actions
Source: https://github.com/qfeius/make-platform-skills/tree/main/skills/make-app-actions
Command: npx skills add https://github.com/qfeius/make-platform-skills --skill make-app-actions-qfeius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @qfei-design/make-app-actions, @qfei-design/canvas-table, and includes references (resource) components.

What problem does it solve? Make CanvasTable record lists need consistent selection-based operations—single edit, single delete, and batch edit—with correct permission checks, denial feedback, and safe handling of selection races. This Skill defines the default consumer-side workflow so hosts integrate the @qfei-design/make-app-actions package correctly instead of hand-rolling action bars, prechecks, and batch modals. ## Core Features & Use Cases - Default selection action bar: Adds selectable rows and a bottom action bar to writable Make record lists, with independent data.record.update, data.record.delete, and data.record.bulkUpdate permissions and a scheme-two empty state when no action is available. - Permission precheck and denial feedback: Freezes an immutable operation snapshot, sends one Service precheck, and maps explicit-mode noPermissionRecordIds to exact error-red row highlighting via CanvasTable setRowColors/clearRowColors while select-all denials stay toast-only. - Batch edit modal integration: Uses AntdRecordBatchEditModal for Ant Design hosts or the generic RecordBatchEditModal with injected design-system components for Arco/shadcn hosts, enforcing the 200-record limit, Shift-selection boundaries, and one bulk Service request. - Use Case: A developer building a Make record list page uses this Skill to wire checkbox selection, row-level write-permission prechecks, and a batch edit dialog that submits a single /data/v1/field mutation without per-record loops. ## Quick Start Use the make-app-actions skill to add the default edit, delete, and batch edit action bar with permission precheck to my Make CanvasTable record list.

Frequently Asked Questions about make-app-actions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add batch edit to a Make CanvasTable record list?

Install @qfei-design/make-app-actions@^0.3.1 and @qfei-design/canvas-table@^1.3.1, enable multiple selection, and use the package action bar with AntdRecordBatchEditModal for Ant Design hosts or the generic RecordBatchEditModal with injected components for other React design systems. Batch edit requires the independent data.record.bulkUpdate permission plus at least one batch-editable field.

How does record selection permission precheck work before editing?

The host freezes an immutable operation snapshot, then sends one Service precheck to the record-write-permission route with the full target. Explicit-mode denials return HTTP 200 with business code 20000032 and noPermissionRecordIds, which the UI maps to exact error-red row highlighting; select-all denials return 403 and stay toast-only.

Can I use the batch edit modal with Arco or shadcn/ui instead of Ant Design?

Yes. Non-AntD React hosts use the generic RecordBatchEditModal and RecordSelectionActionBar, injecting their own Modal, FieldSelect, and ModeControl through MakeAppBatchEditComponents. Do not import AntD into a non-AntD host, and use the installed design system's portal API so popups escape overflow-clipping ancestors.

What is the batch edit record limit and how is Shift selection handled?

Explicit selections allow 1-200 record IDs, and one Shift range-selection gesture may add at most 200 records through the installed CanvasTable public contract. Selections over 200 are blocked with a toast while keeping the selection; CanvasTable 1.3.1 grouped tables do not support Shift range selection and hosts must not emulate it.

Why must batch edit avoid looping single-record update requests?

The Service bulk route sends exactly one Make /data/v1/field request for the whole frozen target. Looping single-record /data/v1/record calls or using runRecordBatchMutation violates the contract, breaks atomic authorization semantics, and multiplies gateway traffic.

When should a Make record list opt out of the default action bar?

Only strictly read-only lists may opt out, and only when read-only is an object or product capability rather than the current user lacking write permissions. A user with no available actions still gets the scheme-two bar showing the selected count, lock icon, and 暂无可用的操作 message.