-
Notifications
You must be signed in to change notification settings - Fork 51
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
Laravel 5.2 incompatibility due to symfony/event-dispatcher #19
Comments
Yes, I will look into it. |
3.* requires PHP 5.5.9 and currently RC PHP SDK supports PHP 5.3. |
I'm currently running 5.5.9 and I haven't noticed any issues with the SDK. |
RC SDK is fully compatible with 5.5.9. The issue is that some of our clients still use PHP 5.3 so we can't upgrade our dependencies right away. We have plans of discarding support of 5.3 and 5.4 in nearest future, within this process I will also upgrade all the dependencies, stay tuned. |
Used GuzzleHttp PSR7 and Client Fix for #19
I have pushed the 2.0.0 candidate to develop branch. You can start using it by having |
I received the following output while installing the SDK via composer in PHP 5.6:
Once I switched the version in |
Is the issue still reproduced on version 2.0.0? |
Is RC v2 only compatible with version symfony/event-dispatcher v3.0? We're using Laravel 5.1 on a project which requires symfony/event-dispatcher ^2.7 making RC v2 incompatible. Would RC v2 potentially work with either "^2.7|^3.3" ? If so, can you update the dependancy in composer to reflect compatibility with either version. |
I have created a branch named "symfony/event-dispatcher": "^2.7|^3.3" Can you validate, please? Just copy this in your composer.json
I would need to vaildate if the same works on 5.2 and does not break the backward compatibility. |
Yup - working fine. Thanks! |
Released 2.1.1 |
There's an incompatibility between laravel 5.2 and ringcentral-php due to symfony/event-dispatcher ^2.7. Laravel currently uses v3.0.1
Would it be possible for ringcentral-php to pump the version up to 3.0.1 also?
The text was updated successfully, but these errors were encountered: