You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had an issue with our Alegra account going over the limit of allowed transactions. The gem was translating the error received from:
{"code":900,"message":"Has llegado al limite de ventas en tu plan actual."}
to:
Status: 402. Error: Required payment!
This was a little confusing since we were calling the Alegra::Client.invoices.create which accepts the payments and paymentMethod fields. We thought the error was referring to those not being present until we debugged the gem and found the original error message.
Is there a way we could return the original message and Alegra error code in the Error? We could submit a PR with that solution if need be.
The text was updated successfully, but these errors were encountered:
Hey @luismendozamx, Please sent the PR I'll be glad to reviewed and accepted.
BTW, sorry for the delay I was kind of busy these days and thanks for reporting the issue
)
* add company class with find action
* add company endpoint wrapper
* add alegra company endpoint basic tests
* add options hash to requests, refactor code a bit and return raw response if option format == raw
* add alegra record.rb and put contacts, payments and all records to inherit from it to refactor a bit
* gitignore byebug history
* pass options to put on company too
* delete byebug historu
* add wrapper with tests for users endpoints
* add categories endpoint wrapper with tests
* adds wrapper for bank accounts endpoint with tests
* details
* update readme
We had an issue with our Alegra account going over the limit of allowed transactions. The gem was translating the error received from:
to:
This was a little confusing since we were calling the
Alegra::Client.invoices.create
which accepts thepayments
andpaymentMethod
fields. We thought the error was referring to those not being present until we debugged the gem and found the original error message.Is there a way we could return the original message and Alegra error code in the Error? We could submit a PR with that solution if need be.
The text was updated successfully, but these errors were encountered: