--- Comment #6 from Brion Vibber <> ---
(In reply to comment #3)
> The issue here is that the Status class is too intertwined with the Message
> class, and this was even before RawMessage was introduced. When you made a
> Status object, it was assumed any error keys were backed by messages.
> The solution should be that the concerns need to be separated. The Status
> class
> should not have anything to do with the Message class. However, that may be a
> bit difficult to achieve, so at the very least there needs to be a separation
> between error codes and message keys.

I'd rather not redo the entire interface of SpecialUserlogin and
ApiCreateAccount just to get this going. Any strong objections to using this
existing approach as a basic fix?

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to