Tickets :: Comment on [#8041] User-facing notifications shouldn't contain stack traces or talk about exceptions

* Your Email Address
* Spam protection	Enter the letters below: . .. ..__.. . __. \|\ \|\|\ \|\| \|\| \|(__ \| \\|\| \\|\|__\\|__\|.__)
Comment	> As far as I understood the outcome was just to not use > error/exception codes for notification classes. My "if you really > want" was rather pointing at the fact that we didn't talk about how > to deal with exceptions in the frontend in H4 at all. Pushing them as > notifications might still be the best solution, but since we re-think > everything, someone might come up with a better idea. > > And to voice my opinion: I still like notifications, though we might > also need a general handler for uncatched exceptions. Heck, I wrote > that stuff 7 years ago. :-)
Attachment
Watch this ticket