Skip to content

docs(skills): document the action and component nav item types #14138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-zhuang merged 3 commits into from
Sep 1, 2026
Merged

docs(skills): document the action and component nav item types #14138

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
66f7ac9
docs(skills): document the action and component nav item types
claude Sep 1, 2026
26e7d75
chore(gates): ratchet the skill-identifier-liveness Leg 2 gap to zero
claude Sep 1, 2026
c587bd7
Merge origin/main into claude/issue-13890-nav-item-types-rows
claude Sep 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions scripts/skill-identifier-liveness-ledger.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,10 +31,5 @@
"note": "Live in ../objectui at packages/plugin-gantt/src/GanttView.tsx, same shift-band prop family as dayStart. Unreachable from this repo's index for the same reason."
}
],
"leg2Gaps": {
"navigation-item-types": [
"action",
"component"
]
}
"leg2Gaps": {}
}
16 changes: 5 additions & 11 deletions skills/objectstack-ui/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -641,6 +641,8 @@ export const CrmApp = App.create({
| `report` | `reportName`, `label`, `icon` | Link to a report |
| `page` | `pageName`, `label`, `icon` | Link to a custom Page (`type: 'home' | 'list' | ...`) |
| `url` | `url`, `label`, `icon` | External or custom URL |
| `action` | `actionDef` (`{ actionName, params? }`), `label`, `icon` | Run an action instead of navigating |
| `component` | `componentRef`, `params?`, `label`, `icon` | Built-in platform component; `componentRef` is a colon-joined registry key (`metadata:resource`), `params` become props |
| `separator` | — | Visual separator |

> **`requiresObject` / `requiresService`:** Use these on any item that
Expand Down Expand Up @@ -2053,23 +2055,15 @@ the selected row in `list_item` contexts.

## Common Pitfalls

1. **Using `provider: 'api'` when `provider: 'object'` is available.**
Object provider gives you free filtering, sorting, pagination, and
real-time updates.

2. **Putting too many columns in a grid view.**
1. **Putting too many columns in a grid view.**
Users rarely need more than 6–8 columns visible by default. Use `hidden`
for secondary columns.

3. **Forgetting `link: true` on the primary column.**
2. **Forgetting `link: true` on the primary column.**
The first meaningful column (usually the name/subject) should be the
navigation link to the record detail.

4. **Not setting quick filters.**
Quick filters dramatically improve usability. Always add at least a
"My Records" filter using `$currentUser`.

5. **Putting widget grid placement in `position`.**
3. **Putting widget grid placement in `position`.**
The grid-placement field is `layout: { x, y, w, h }` — `position` is not a
widget key and the closed schema REJECTS it by name (it was silently
dropped before protocol 17). `layout` is optional: omit it and the widget
Expand Down
Loading