Page MenuHomePhabricator

[lib] Use getMessageForException instead of e.message in DM related code
ClosedPublic

Authored by angelika on Oct 21 2024, 1:28 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Dec 4, 11:11 AM
Unknown Object (File)
Wed, Dec 4, 11:11 AM
Unknown Object (File)
Wed, Dec 4, 11:11 AM
Unknown Object (File)
Wed, Dec 4, 11:10 AM
Unknown Object (File)
Wed, Dec 4, 11:10 AM
Unknown Object (File)
Wed, Dec 4, 10:53 AM
Unknown Object (File)
Sat, Nov 23, 10:13 AM
Unknown Object (File)
Sat, Nov 23, 3:20 AM
Subscribers

Details

Summary

Use getMessageForException instead of e.message in DM related code in order to avoid bugs when throwing primitives.
Depends on D13757

Test Plan
  1. Run flow checks, run the app, verify that nothing crashes.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable