You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: Homepage is missing available cards/widgets from new frontend system #5325
in workspaces/homepage, there is a backstage app with new frontend system. But the custom implementation of the homepage loads only configured cards as available cards, not all new frontend system cards. Can you research that problem.
applyDefaultWidgetsToNfsWidgets() in src/components/applyDefaultWidgets.ts acts as a strict allowlist: it iterates over the backend's defaultWidgets entries and only keeps NFS widgets whose extension name matches a ref. Any widget attached to page:homepage that isn't in the backend configuration is silently dropped from the result.
Recommended fix
After building the ordered result from defaultWidgets, append any remaining input widgets that had no matching defaultWidget entry. This preserves backend-driven ordering and persona filtering for known widgets while still surfacing third-party or newly registered NFS widgets as available cards.
Proposed test case
it('includes widgets that have no matching defaultWidgets ref',()=>{constwidgets=[widget('quickaccess-card'),widget('third-party-widget'),];constresult=applyDefaultWidgetsToNfsWidgets(widgets,[{id: 'qa',ref: 'quickaccess-card'},]);expect(result).toHaveLength(2);expect(result.map(getHomepageWidgetExtensionName)).toContain('third-party-widget');});
Labels: Bug in the homepage workspace — matches the repo convention of pairing a type label with a workspace label.
Next steps:
/fs-code — agent creates a PR to implement this issue
/fs-code <your instruction> — agent implements with your specific guidance
/fs-code just show all NFS widgets under add widgets. No filtering needed. Widgets from the backend should match that and can be ignored if the NFS extension id is missing.
Activity
christoph-jerolimov commentedon Oct 22, 2026
/fs-triage
fullsend-ai-triage commentedon Oct 22, 2026
🤖 Finished Triage · ✅ Success · Started 10:41 PM UTC · Completed 10:46 PM UTC
Commit:
7433085· View workflow run →Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.26
fullsend-ai-triage commentedon Oct 22, 2026
Root cause
applyDefaultWidgetsToNfsWidgets()insrc/components/applyDefaultWidgets.tsacts as a strict allowlist: it iterates over the backend'sdefaultWidgetsentries and only keeps NFS widgets whose extension name matches aref. Any widget attached topage:homepagethat isn't in the backend configuration is silently dropped from the result.Recommended fix
After building the ordered result from
defaultWidgets, append any remaining input widgets that had no matchingdefaultWidgetentry. This preserves backend-driven ordering and persona filtering for known widgets while still surfacing third-party or newly registered NFS widgets as available cards.Proposed test case
Labels: Bug in the homepage workspace — matches the repo convention of pairing a type label with a workspace label.
Next steps:
/fs-code— agent creates a PR to implement this issue/fs-code <your instruction>— agent implements with your specific guidancechristoph-jerolimov commentedon Oct 22, 2026
/fs-code just show all NFS widgets under add widgets. No filtering needed. Widgets from the backend should match that and can be ignored if the NFS extension id is missing.
fullsend-ai-coder commentedon Oct 22, 2026
🤖 Finished Code · ✅ Success · Started 10:50 PM UTC · Completed 11:01 PM UTC
Commit:
7433085· View workflow run →Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.91