Open kmichalak opened 2 years ago
👋 @kmichalak apologies for the delay in a reply, and thanks so much for this issue and for your thorough notes 😻
Should the SDK code be aligned in this area with what documentation says, or some values are skipped on purpose?
Our reference docs should be considered the source of truth. This definitely sounds like we have some auditing and process cleanup to do on our side so that new validation errors are getting added to the SDKs. Thanks again for bringing this to our attention. I don't have an ETA on when this will be rectified, but now that we're aware it will eventually be resolved.
I can say that some of these validation errors should only be returned on the client and would not be returned from a server side call in the Java SDK. This leads me to think we may want to make that distinction more clear in our docs... Taking this to our docs team for thoughts, too.
for internal tracking, ticket 1974
Hi @hollabaq86
It's been a while since the last update. Did anything happen in thsi area? One of the greatest misteries for me is the validation error code 915197
:)
General information
Issue description
I checked documentation at https://developer.paypal.com/braintree/docs/reference/general/validation-errors/all and compared it to the list of enum values provided by class
com.braintree.ValidationErrorCode
. A lot of error codes are missing (over 300). In a result it's a bit hard to handle some error responses from Brainrtee gateway and react to them. I understand that some of them are marked as deprecated and might disappear, but they probably should be removed after gateway will stop returning them. Also some error codes are returned and not included in the enum at all. Also I'm pretty aware that some codes are not mentioned in documentation or code, but gateway still returns some of them, like for exmaple`
915197
` but I'm not able to figure out if these is just an experimental error code or is something that was missed in docs.
Should the SDK code be aligned in this area with what documentation says, or some values are skipped on purpose? I'll be happy to help with updating the enum if that's a "missing feature" :)
Full list of missing (documented) codes and their descriptions can be found below