fix: extract message from WASM SDK error objects in toError()#20
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |


When the Dash SDK throws an error from a WASM-based operation, it throws a plain object with a
messageproperty rather than a standard JSErrorinstance. ThetoError()utility was falling through toString(value)for these, producing the unhelpful[object Object]shown in the UI error panel.This fix adds a check for objects with a
messageproperty before the string fallback, so WASM SDK errors now display their actual human-readable message. The change covers all error paths in the app since everycatchblock routes throughtoError().Changes
toError()insrc/ui/state.tsto extractmessagefrom non-Errorobjects before falling back toString(value)Summary by CodeRabbit