Display debug information directly on the page to diagnose
why modules list is empty. Shows:
- Data type received
- Whether it's an array
- Full JSON dump of the data
This will help identify the exact structure being returned.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Added modules-debug.js with extensive console logging to
diagnose why modules page shows empty even though backend
returns data correctly.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Fixed modules page showing empty list even though backend
returns data correctly.
Problem:
- RPC declare with expect: { modules: [] } automatically
extracts the 'modules' field from the JSON response
- This means data is already the array, not an object
- Code was using data.modules which was undefined
- Fell back to empty array []
Solution:
- Use data directly instead of data.modules
- Added comment explaining the behavior
Backend returns: { "modules": [...] }
RPC expect extracts: [...]
So data = [...] not { modules: [...] }
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
