-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the library usable without the \Recurly_Client::$apiKey #318
Comments
Could you say more about the goal of multiple clients? I'd think resources would preserve the client they were initialized with and pass that on other resources that they load. |
We're having two client for billing inside USA and outside USA (I don't know the details, however it seems required for legal reasons) Resource preserve the client they were initialized with except in some edge case, when
|
@romainneutron can you provide any example code as to how you are trying to accomplish this? |
I'd love to see the library updated to not use static at all and name spaced. At the moment, it feels very uncomfortable to use. |
@nsanden I think we agree on the principle, but that would mean a very difficult upgrade path for our customers. |
php sdk v2 perhaps :) |
Closing out this issue due to the fact that it will not be implemented in this major version of the library |
It would be great if the library would be usable without the static property. It would allow us to have multiple recurly clients instantiated at the same time.
At the moment, the
__createNodeObject
factory inbase.php
prevents us to do that.The text was updated successfully, but these errors were encountered: