Closed
Bug 887471
Opened 11 years ago
Closed 11 years ago
Display user errors with useful developer error codes
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-09-03
People
(Reporter: kumar, Assigned: kumar)
Details
When a webpay error happens we need to accomplish two things: - inform the user what happened while they were attempting a purchase - inform the developer what happened in case they made a programming mistake while using the APIs, keys, etc Let's make the user informative error and use some kind of alternate short-error (a code?) that developers can use. If we go with a code, let's try to make it readable, not numeric.
Assignee | ||
Updated•11 years ago
|
Priority: -- → P2
Comment 1•11 years ago
|
||
A code that is greppable and understandable with a sane heirarchy: price.tier.unavailable for example would work for me.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → kumar.mcmillan
Assignee | ||
Updated•11 years ago
|
Target Milestone: --- → 2013-07-25
Assignee | ||
Updated•11 years ago
|
Target Milestone: 2013-07-25 → 2013-08-01
Assignee | ||
Updated•11 years ago
|
Target Milestone: 2013-08-01 → 2013-08-08
Assignee | ||
Updated•11 years ago
|
Target Milestone: 2013-08-06 → 2013-08-13
Updated•11 years ago
|
Version: 1.0 → 1.3
Assignee | ||
Updated•11 years ago
|
Target Milestone: 2013-08-13 → 2013-08-27
Updated•11 years ago
|
Target Milestone: 2013-08-27 → 2013-09-03
Assignee | ||
Comment 2•11 years ago
|
||
First pass at fixing: https://github.com/mozilla/webpay/commit/0f61f2fe375adbdea9165f7e65964d4ed3dba90c We still need to convert the remaining errors to codes and expose the legend somehow
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•