Uh oh!
There was an error while loading. Please reload this page.
Add support for calling the invoicing API - #52
Conversation
lsolesen
commented
May 19, 2017
Thanks for the pull request. Do you mind writing a test case scenario for the change, so we avoid problems in future releases? |
lsolesen
commented
Jul 25, 2017
@Sthing What about introducing a new class for the Invoicing API so the resulting end code will be more clear? And that class utilize the client with the url? |
lsolesen
commented
Sep 14, 2017
@Sthing What is your take on my suggestion for introducing another class for starting up the Invoice API? |
Sthing
commented
Sep 14, 2017
@lsolesen Ehm - I think it is ok, but I don't have the time to do it right now. |
welrachid
commented
Apr 27, 2023
Not sure this is still relevant. i made this solution, so i dont have to deal with multiple classes, since the only difference is the api endpoint. The rest is the same and therefore no need for another class. |
No description provided.