error diagnostics registry/UI for errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Silva |
Fix Released
|
Low
|
Guido Wesdorp |
Bug Description
In some cases, we get errors which are easily diagnosed by
looking at the exception type and string and
which may recurr in multiple releases. The best candidate of
this is the UnicodeError. Unauthorized is another (but more
complicated) example.
In this case, it is more user friendly to present a better
diagnostic than just the traceback. In case of unicode
errors this could for instance be something like (VERY
rough draft):
Text handling problem. Silva received some characters
it could not deal with for some reason. This is very
likely to be a bug we would like to hear about.
[button] presents an email message with diagnostic
information which you can send to the developers through
<email address hidden>. Please describe what you were doing
at the time (were you editing? previewing? What element
did you change just before the error occured?)
In case of unauthorized we already intercept and display
a link to request authorization. In some cases this could
be due a bug in Silva however, so we should mention
something about this as well.
We need to handle this on an error by error basis; some
errors it is very hard to provide sensible diagnostics
about (think IndexError for instance), except that it
"it is an error". But in other cases this could help the
user experience and provide us with more information.
We need to start experimenting with this soon if we
want to make 0.9.2. Guido, interested in this? It
involves a registry. ;)