Since this module was last updated, Xero have fully implemented OAuth 2-based authentication, and deprecated OAuth 1 applications. It is no longer possible to register an OAuth 1 application with Xero, so no-one new can use this module.
In the new world there is no concept of Public vs Private vs Parter - there's just applications, all of which have the potential to be public. Applications can either be published under the marketplace or not. So you can still have a private application of sorts by just not publishing it and only allowing yourself to connect to it.
In some ways this is an improvement, as it significantly simplifies the required code. However, it is not a small change; authentication has to be rebuilt using a new OAuth library, and everything restructured to account for there only being one application type, documentation, tests etc. I submit that a breaking change is necessary.
The other perl Xero module has not been updated to account for this change either. I have an immediate business need for this to be implemented, and will thus begin working on it full time as of now. I have started a new branch at https://github.com/realflash/WebService-Xero/tree/oauth2
If currrent maintainer(s) no longer want to work on this module I am happy to adopt it - I am already the developer and maintainer of several other perl modules.
Are there any thoughts as to whether this should be a whole different module name? My thought is not, just to issue a breaking change.
Since this module was last updated, Xero have fully implemented OAuth 2-based authentication, and deprecated OAuth 1 applications. It is no longer possible to register an OAuth 1 application with Xero, so no-one new can use this module.
In the new world there is no concept of Public vs Private vs Parter - there's just applications, all of which have the potential to be public. Applications can either be published under the marketplace or not. So you can still have a private application of sorts by just not publishing it and only allowing yourself to connect to it.
In some ways this is an improvement, as it significantly simplifies the required code. However, it is not a small change; authentication has to be rebuilt using a new OAuth library, and everything restructured to account for there only being one application type, documentation, tests etc. I submit that a breaking change is necessary.
The other perl Xero module has not been updated to account for this change either. I have an immediate business need for this to be implemented, and will thus begin working on it full time as of now. I have started a new branch at https://github.com/realflash/WebService-Xero/tree/oauth2
If currrent maintainer(s) no longer want to work on this module I am happy to adopt it - I am already the developer and maintainer of several other perl modules.
Are there any thoughts as to whether this should be a whole different module name? My thought is not, just to issue a breaking change.