ErrorResult could use a top-level 'code' attribute to match the 'message' attribute

[foresto]

The ErrorResult class has a top-level message attribute which is a convenient alternative to groveling through the children of errors when only the first/main error message is needed for display. Unfortunately, there is no matching code attribute, so there's no good way to take programmatic action based on what kind of error it is.

As far as I can tell, there is also no documentation indicating which child of errors was used for the top-level message, so grabbing an error code from there would seem unreliable at best.

[braintreeps]

Result objects have a deep_errors attribute that returns a flattened list of all errors at all levels. You can simply grab the code of the first error, or grab all of the codes, and take programmatic action based on the codes you see.

Take a look at http://www.braintreepaymentsolutions.com/docs/python/general/validation_errors#all_errors_on_all_levels

Please let us know if deep_errors does not accomplish what you are looking for.

[foresto]

Right, I'm aware of deep_errors and can get by with it. This issue is really more of a feature request than a bug. The top-level message would be more generally useful if it had a matching code attribute, to bring it into parity with all the other error objects in an ErrorResult. Failing that, it would be nice at least to have documentation indicating which of the errors in deep_errors is represented by the top level message.

[braintreeps]

The top level message is a string containing all of the error messages (validation errors, processor declined, etc). Since there can be more than one error, there is no one code that matches. We will update the docs to make this more clear.