039db99307
Both plugins declared dashboardViews only in their src/index.ts module. PluginLoader.getCurrentManifestDashboardViews treats a successfully-read manifest as authoritative and returns an empty list when the key is absent, and getPluginDashboardViews only falls back to the module definition when the manifest read fails. The module-level entries were therefore discarded and neither view appeared on any nav surface -- header overflow, desktop sidebar, or mobile More sheet all consume the same array from usePluginDashboardViews. Mirror the manifest shape used by fusion-plugin-compound-engineering. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
17 lines
373 B
JSON
17 lines
373 B
JSON
{
|
|
"id": "fusion-plugin-todos",
|
|
"name": "Todo Lists",
|
|
"version": "0.1.0",
|
|
"description": "Project-scoped todo lists that hand items into Fusion planning.",
|
|
"dashboardViews": [
|
|
{
|
|
"viewId": "todos",
|
|
"label": "Todos",
|
|
"componentPath": "./dashboard-view",
|
|
"icon": "CheckSquare",
|
|
"placement": "overflow",
|
|
"order": 70
|
|
}
|
|
]
|
|
}
|