Compatibility with PHP Library 2.10 and above

Hate to RTBC my own patch so much later, but any chance of getting this committed? We are still relying on a fork of this module that's very outdated at this point. Would love to kill it and bring us back up to date.

Could I maybe get an update on the status of this issue, and why it's necessary. Reading back through the issue I'm a little bit confused about where things are at now. I just checked, and the V2 client continues to be supported by Recurly https://github.com/recurly/recurly-client-php/tree/v2, and has been updated to their v2.14.x API as of a few weeks ago. I know we're using the 4.x branch of the module with the version 2.14.0 of the PHP library and it's been working fine.

I'm pretty hesitant to use a mirror of the v2 library that hasn't been updated in years https://github.com/hfischberg/v2Recurly-client when the official library continues to get updates.

@eojthebrave I see the confusion. Back when #37 was written, https://github.com/hfischberg/v2Recurly-client was created for me by a recurly support member, and it seemed that the v2 branch would be sunset. Their versioning is confusing (for me, at least), because the api version differs from the SDK version. The latest v2 api on https://recurly.com/developers/api-v2/ is 2.29, which is the same latest release as 3 years ago, while the recent 2.x release on github is 2.14.1.

To compound my confusion, they also have 3.x and 4.x releases that both seem to relate to the v3 api, without documentation as to what the difference is.

You're probably right that it doesn't make sense for this module to use that fork given that it's way out of date and 2.x continues to receive updates. I guess maybe my team is just in the unfortunate situation of needing to run both v2 and v3 concurrently. In an ideal world, we could have an up-to-date v2 package separate from the v3 package, but I don't know that there's a good way to do that unless one of us wanted to maintain a fork to track 2.x.

This doesn't really offer a solution, but I think this essentially summarizes where things stand.

Maybe the "real" solution to this would be to update the Recurly module itself to use the v3 api. Likely not a small undertaking, and y'all could weigh the benefits of such a move. I'd be happy to help with this update if we want to go that route.

update the Recurly module itself to use the v3 api

This is definitely my long term goal. I've been slowly working on adding tests in ✨ Improve test coverage Needs work thinking that having decent test coverage will make that update easier since we'll be able to feel more confident that things are working. But I haven't yet really dug into what all the update would entail.

Also FWIW I totally agree the versioning of the API versus the PHP library is super confusing.