Add actions and form_layout sections to CRM example metadata

[Copilot]

CRM example was missing actions and form_layout — two of the three spec capabilities needed for end-to-end Console verification.

Actions (21 total)

Top-level actions array added to defineStack() covering all 8 objects:

• Account: Send Email, Assign Owner, Merge Accounts
• Contact: Send Email, Convert to Customer, Log a Call
• Opportunity: Change Stage, Mark as Won, Mark as Lost
• Product: Toggle Active, Update Price
• Order: Change Status, Generate Invoice, Mark as Shipped
• User: Reset Password, Deactivate User
• Project Task: Change Status, Assign User
• Event: Send Invitation, Mark as Completed, Cancel Event

Exercises params (select/text/email/textarea/boolean/currency/lookup), confirmText, variant (primary/danger), locations (record_header/list_item/record_more), refreshAfter, successMessage.

Form Layouts (29 sections across 8 objects)

form.sections added to each view entry:

form: {data: {provider: 'object',object: 'account'},sections: [{label: 'Basic Information',columns: '2',fields: ['name','industry','type', ...]},{label: 'Financial',columns: '2',fields: ['annual_revenue','tags']},{label: 'Address',columns: '2',fields: ['billing_address','shipping_address', ...]},{label: 'Additional Details',columns: '1',collapsible: true,fields: ['description', ...]},],},

Each object gets 3–4 sections with logical field grouping, multi-column layouts, and collapsible detail sections.

Metadata split into per-object files

Views and actions are organized into separate files following the existing src/objects/ pattern:

• src/views/ — 8 files (account.view.ts, contact.view.ts, opportunity.view.ts, product.view.ts, order.view.ts, user.view.ts, event.view.ts, project.view.ts)
• src/actions/ — 8 files (account.actions.ts, contact.actions.ts, opportunity.actions.ts, product.actions.ts, order.actions.ts, user.actions.ts, event.actions.ts, project.actions.ts)
• objectstack.config.ts reduced from 1418 → 770 lines, now imports and spreads from separate files
• src/index.ts re-exports all new modules

Note

objectstack compile has a pre-existing re-validation bug on form.sections.columns (Zod transforms string "2" → number 2, then re-validates against the string enum). defineStack() itself accepts the config correctly.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Enrich CRM example metadata with full @objectstack/spec capabilities</issue_title>
<issue_description>

🎯 Goal

Maximize the CRM example's use of @objectstack/spec features so that the Console front-end can verify all platform capabilities end-to-end.

📦 What's Being Enhanced

All 8 Object Definitions (account, contact, opportunity, product, order, user, project_task, event):

Enhancement	Description
Object metadata	description, titleFormat, recordName
Field enrichments	required, searchable, unique, defaultValue, helpText, placeholder, group, readOnly
Field type diversity	text, textarea, richtext, email, url, number, currency, percent, date, datetime, boolean, select (with colors), multi-select, lookup (single/multiple)
list_views	2+ list views per object (All, Active/Filtered) with sort/filter
actions	Object-level actions (Send Email, Change Status, etc.) to exercise the Action Engine
form_layout	Sections-based form layout organizing fields into logical groups
New fields	30+ new fields across all objects (tags, avatar, linkedin, expected_revenue, shipping_address, etc.)

Config & Docs Updates:

• objectstack.config.ts — Updated seed data, new views leveraging new fields
• ROADMAP.md — Completion entry added

🔑 Key Principle

• Only use features actually supported by ObjectSchema.create() and Field.*() from @objectstack/spec/data
• Keep backward compatibility with existing seed data field names
• Run tests to ensure nothing breaks

The coding agent is now working on the PR. You'll receive a notification when it's ready for review. 🚀</issue_description>

Comments on the Issue (you are @copilot in this section)

@hotlong 任务没完成 list_views | 2+ list views per object (All, Active/Filtered) with sort/filter -- | -- actions | Object-level actions (Send Email, Change Status, etc.) to exercise the Action Engine form_layout | Sections-based form layout organizing fields into logical groups

• FixesEnrich CRM example metadata with full @objectstack/spec capabilities #655

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectui	Ready	Preview, Comment	Feb 20, 2026 3:01pm
objectui-demo	Error		Feb 20, 2026 3:01pm
objectui-storybook	Ready	Preview, Comment	Feb 20, 2026 3:01pm

[hotlong]

元数据应该分拆成单独的文件 @copilot

[Copilot]

元数据应该分拆成单独的文件 @copilot

Done in 9ca0076. Split metadata into per-object files:

• src/views/ — 8 files (account.view.ts, contact.view.ts, etc.) with listViews + form sections
• src/actions/ — 8 files (account.actions.ts, contact.actions.ts, etc.) with object-level actions
• objectstack.config.ts reduced from 1418→770 lines, now imports and spreads from separate files
• src/index.ts re-exports all new modules

[Copilot]

Pull request overview

Adds missing CRM example metadata to better exercise Console features end-to-end by introducing stack-level actions and form section layouts, and organizing the metadata into per-object modules.

Changes:

• Added per-object views/* modules that include form.sections (form layout) and multiple listViews.
• Added per-object actions/* modules and registered them in the CRM stack config.
• Updated exports and ROADMAP entry to reflect the enrichment.

Reviewed changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 17 comments.

Show a summary per file

File	Description
examples/crm/objectstack.config.ts	Imports new per-object view/action modules; registers actions and swaps inline views for module references.
examples/crm/src/index.ts	Re-exports newly added views/* and actions/* modules for easier consumption.
examples/crm/src/views/account.view.ts	Adds form.sections layout and maintains 2 list views for Account.
examples/crm/src/views/contact.view.ts	Adds form.sections layout and maintains 2 list views for Contact.
examples/crm/src/views/opportunity.view.ts	Adds form.sections layout and multiple list views including kanban pipeline.
examples/crm/src/views/product.view.ts	Adds form.sections layout and maintains 2 list views for Product.
examples/crm/src/views/order.view.ts	Adds form.sections layout and maintains 2 list views for Order.
examples/crm/src/views/user.view.ts	Adds form.sections layout and maintains 2 list views for User.
examples/crm/src/views/event.view.ts	Adds form.sections layout and list views including a calendar view.
examples/crm/src/views/project.view.ts	Adds form.sections layout and list views including gantt/timeline entries.
examples/crm/src/actions/account.actions.ts	Introduces Account actions with confirm/success metadata and parameter definitions.
examples/crm/src/actions/contact.actions.ts	Introduces Contact actions with confirm/success metadata and parameter definitions.
examples/crm/src/actions/opportunity.actions.ts	Introduces Opportunity actions with confirm/success metadata and parameter definitions.
examples/crm/src/actions/product.actions.ts	Introduces Product actions with parameter definitions.
examples/crm/src/actions/order.actions.ts	Introduces Order actions with confirm/success metadata and parameter definitions.
examples/crm/src/actions/user.actions.ts	Introduces User actions with confirm/success metadata.
examples/crm/src/actions/project.actions.ts	Introduces Project Task actions with parameter definitions.
examples/crm/src/actions/event.actions.ts	Introduces Event actions with confirm/success metadata and parameter definitions.
ROADMAP.md	Updates the CRM enrichment entry to include actions + form_layout sections.

[Copilot]

These actions are declared as type: 'api' but don't provide endpoint/api/target. In the current ActionRunner implementation, type: 'api' without an endpoint returns No API endpoint provided, so clicking these will always fail. Consider either supplying a dummy endpoint (if you want to exercise API execution) or switching these example actions to a non-network type (e.g. script) so Console verification can reach success/refresh flows.

[Copilot]

params: [...] is used here as parameter schema, but ActionRunner expects actionParams for param collection and uses params for runtime values/body. As-is, the param collection dialog won’t trigger. Align with the runner (or add a translation step in the Console executor).

[Copilot]

params: [...] is being used as parameter definitions, but ActionRunner’s param dialog is driven by actionParams and treats params as runtime values. If you want to exercise param collection, align the field name or translate it before execution.

[Copilot]

params: [...] is used as parameter definitions here, but ActionRunner’s param collection is keyed off actionParams and treats params as runtime values. To actually exercise param collection in Console, align the schema (or translate spec params → runner actionParams).

[Copilot]

These actions use params: [...] as parameter definitions. In ActionRunner, param collection is driven by actionParams (definitions) and params is treated as runtime values/body. If you want the Console to pop a parameter dialog, either export definitions under actionParams or add a mapping layer that translates spec params into actionParams before execution.

[Copilot]

These actions are type: 'api' but don’t specify endpoint/api/target. In the current ActionRunner this makes execution fail with No API endpoint provided. Add endpoints (mock/placeholder is fine) or switch to an action type that can succeed without a network call.

[Copilot]

Timeline view defaults in Console use dateField: 'due_date' when no timeline.dateField is provided. project_task doesn’t have due_date, so this Timeline view will render with missing/invalid dates. Add an explicit timeline config (e.g., set the date field to start_date, and optionally endDateField to end_date) so the Timeline view is actually usable.

Suggested change

	columns: ['name','start_date','status'],
	columns: ['name','start_date','status'],
	timeline: {
	dateField: 'start_date',
	endDateField: 'end_date',
	},

[Copilot]

These type: 'api' actions have no endpoint/api/target, so ActionRunner execution will fail with No API endpoint provided. Provide endpoints (even placeholder/mock) or switch to a non-API action type so these actions can actually be run in Console.

[Copilot]

These actions are type: 'api' without any endpoint/api/target. With the current ActionRunner, executing them always fails (No API endpoint provided). Provide endpoints or use a non-API type so the actions can succeed during Console verification.

[Copilot]

The closing_this_month view is labeled “Closing This Month” but doesn’t define any filter criteria, so it will show the same records as the unfiltered list (just with a sort). Either add a close_date-based filter (if supported by the spec/runtime) or rename the view label/id to avoid implying date filtering that isn’t happening.