| Nikerabbit added a comment. |
Drive-by comments: defaulting to html for error messages might not be a good idea. On the other hand, the mix if html and non-html is not good either. Should we do both by stripping html into plaintext?
We should also consider making it more explicit what kind of errors the API can return so that clients can be prepared. I am also wondering how to strike the balance of forcing clients to use proper errors related to the user's task instead of generic "failed to save the page".
Would it be possible to loop-in frontend standard groups to think of some standard ways of displaying errors and warnings instead of every system having to do it from scratch?
TASK DETAIL
EMAIL PREFERENCES
To: Anomie, Nikerabbit
Cc: Nikerabbit, Tgr, bearND, MZMcBride, Fhocutt, Aklapper, Ricordisamoa, Wikidata-bugs, Anomie, He7d3r, Catrope, Yurik, wikibugs-l-list, Reedy, daniel, PleaseStand, Sethakill, dg711, jayvdb, Legoktm
Cc: Nikerabbit, Tgr, bearND, MZMcBride, Fhocutt, Aklapper, Ricordisamoa, Wikidata-bugs, Anomie, He7d3r, Catrope, Yurik, wikibugs-l-list, Reedy, daniel, PleaseStand, Sethakill, dg711, jayvdb, Legoktm
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
