mitai-jinkendo/frontend
Lars 9c8859b1ae
All checks were successful
Deploy Development / deploy (push) Successful in 47s
Build Test / lint-backend (push) Successful in 0s
Build Test / build-frontend (push) Successful in 15s
fix: React error #31 - Cannot render signal objects directly
Root Cause:
- WorkflowResultViewer tried to render NormalizedSignal objects directly
- React Error #31: "Objects are not valid as a React child"
- Caused white screen crash after workflow execution

Frontend WorkflowResultViewer.jsx:
- Fixed signal rendering in "All Signals" section
- Now displays: question_type: normalized_value (status)
- Proper formatting for signal objects

Before:
  • {signal}   renders [object Object]

After:
  • protein_intake: optimal (valid) 

Impact:
- Workflow execution no longer crashes the UI
- Signals are properly displayed
- Users can see normalized decision signals

Issue: White screen after workflow execution
Version: 0.9p (workflow module)
Part 3: End Node Template Engine - UI Fix

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-09 18:38:09 +02:00
..
public feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00
src fix: React error #31 - Cannot render signal objects directly 2026-04-09 18:38:09 +02:00
Dockerfile feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00
index.html feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00
nginx.conf feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00
package-lock.json feat: Phase 5 - Visual Workflow Editor (Option B) 2026-04-04 17:56:00 +02:00
package.json feat: Phase 5 - Visual Workflow Editor (Option B) 2026-04-04 17:56:00 +02:00
vite.config.js feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00