On Tuesday, November 26, 2013 09:52:37 PM Matthew Toseland wrote: > On 30/10/13 03:47, xor wrote: > >>>> Errors: > >>>> If you are already subscribed to the selected type, you will only > >>>> receive > >>>> a > >>>> message: > >>>> "Message" = "Error" > >>>> "Description" = > >>>> "plugins.WebOfTrust.SubscriptionManager$SubscriptionExistsAlreadyExcept > >>>> io > >>>> n" > >>>> "SubscriptionID" = Same as in the original "Subscribed" message > >>>> "To" = Same as you requested > >>>> "OriginalMessage" = "Subscribe" > >> > >> Would it be appropriate to have an error code so that some error types > >> can be machine-readable? I remember running into difficulties with this > >> sort of thing with my Infocalypse patches. > > > > The "Description" is the actual class name of the exception, so it should > > be safe to assume that the same literal value is always used. > > Until you refactor. This is bad IMHO, you should have a defined list of > error codes (even if you use strings for them, they shouldn't include > e.g. package names).
ACK. Bug filed at: https://bugs.freenetproject.org/view.php?id=6280
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
