[PR #30253] fix(web): handle null/undefined message in log list #32748

Closed
opened 2026-02-21 20:52:00 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/langgenius/dify/pull/30253

State: closed
Merged: Yes


Summary

  • Add null safety checks for message, feedbacks, and provider_response_latency properties

Changes

  • Use nullish coalescing (??) for item.message to prevent spread operator error
  • Use optional chaining (?.) for item.feedbacks.find() calls
  • Add fallback value for item.provider_response_latency.toFixed()

fixes #28279

**Original Pull Request:** https://github.com/langgenius/dify/pull/30253 **State:** closed **Merged:** Yes --- ## Summary - Add null safety checks for message, feedbacks, and provider_response_latency properties ## Changes - Use nullish coalescing (`??`) for `item.message` to prevent spread operator error - Use optional chaining (`?.`) for `item.feedbacks.find()` calls - Add fallback value for `item.provider_response_latency.toFixed()` fixes #28279
yindo added the pull-request label 2026-02-21 20:52:00 -05:00
yindo closed this issue 2026-02-21 20:52:00 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#32748