We found a case where the errors node is nested within the response from the User Registration API. Originally we were only looking at the first level for the errors node, but this is deeper.
The solution is we look at the first level for the errors node, but then look one level deeper for it. If the response is nil, we return blank as it originally did. Also did a little boyscouting in changing the old 'fail error' to the newer 'raise error'.
We found a case where the errors node is nested within the response from the User Registration API. Originally we were only looking at the first level for the errors node, but this is deeper. The solution is we look at the first level for the errors node, but then look one level deeper for it. If the response is nil, we return blank as it originally did. Also did a little boyscouting in changing the old 'fail error' to the newer 'raise error'.
Staging: Uses a pregem version of the gem along with some changes I have in a C-M branch. http://m-car-ins.cbmtn.io/user/register
Response: