[Tickets #8041] Re: User-facing notifications shouldn't contain stack traces or talk about exceptions
bugs at horde.org
bugs at horde.org
Mon Mar 2 23:55:53 UTC 2009
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/8041
------------------------------------------------------------------------------
Ticket | 8041
Updated By | Jan Schneider <jan at horde.org>
Summary | User-facing notifications shouldn't contain stack
| traces or talk about exceptions
Queue | IMP
Version | Git master
Type | Bug
State | Assigned
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Slusarz
------------------------------------------------------------------------------
Jan Schneider <jan at horde.org> (2009-03-02 18:55) wrote:
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. :-)
More information about the bugs
mailing list