feat(error-handling): generalize snack error with fallback#176
Conversation
Replace `snackError({ messageTxt: error.message, ... })` patterns with
`snackWithFallback(snackError, error, { ... })` so that structured errors
(ProblemDetailError, NetworkTimeoutError) raised by backendFetch are
surfaced with their business code / technical details, while plain
errors keep the previous behavior via catchErrorHandler.
Signed-off-by: Florent MILLOT <florent.millot_externe@rte-france.com>
📝 WalkthroughWalkthroughError handling across thirteen UI components has been unified to use a ChangesError handling unification using snackWithFallback
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
… of snackWithFallback Remove handleAnnouncementCreationErrors and its dedicated translation keys since snackWithFallback now covers these cases generically. Signed-off-by: Florent MILLOT <florent.millot_externe@rte-france.com>
|



Summary
snackError({ messageTxt: error.message, ... })patterns withsnackWithFallback(snackError, error, { ... })across the app so that structured errors raised bybackendFetch/backendFetchJsonare surfaced with their business code or technical details.Notes