Skip to content

fix: resolve API_BASE ReferenceError and category filter in Extensions page#732

Merged
Lightheartdevs merged 1 commit intoLight-Heart-Labs:mainfrom
yasinBursali:fix/extensions-jsx-api-base-and-category-filter
Apr 3, 2026
Merged

fix: resolve API_BASE ReferenceError and category filter in Extensions page#732
Lightheartdevs merged 1 commit intoLight-Heart-Labs:mainfrom
yasinBursali:fix/extensions-jsx-api-base-and-category-filter

Conversation

@yasinBursali
Copy link
Copy Markdown
Contributor

What

  • Fix ReferenceError: API_BASE is not defined in ConsoleModal log polling
  • Fix category filter dropdown missing categories from secondary features

Why

  • API_BASE was never declared in Extensions.jsx — the poll() function crashed on every call, preventing auto-refresh of extension logs
  • Category derivation only read features[0].category, ignoring categories from features[1+]

How

  • Replace ${API_BASE}/api/extensions/... with relative URL /api/extensions/... (matching fetchLogsOnce)
  • Replace .map(ext => ext.features?.[0]?.category) with .flatMap(ext => ext.features?.map(f => f.category) || [])

Testing

  • npm run build
  • npm run lint ✅ (0 errors)

Platform Impact

All platforms (browser-side fix)

🤖 Generated with Claude Code

…s page

Replace undefined API_BASE variable in ConsoleModal poll() with relative
URL matching fetchLogsOnce(). Collect categories from all extension
features instead of only the first one.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Lightheartdevs Lightheartdevs merged commit 5028857 into Light-Heart-Labs:main Apr 3, 2026
19 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants