[L5.2] Update composer.json

[php-tmdb]

[L5.2] Update composer.json

[wtfzdotnet]

Could you create a fork with this update and submit a pull request for @MarkRedeman to review? I'm not involved with Laravel so I have no clue what implications there are for backwards compatibility. While you wait for a merge of this fix you can refer to your own fork ( http://mnapoli.fr/overriding-dependencies-with-composer/ ).

[MarkRedeman]

This is currently not possible because TMDB/API depends on version ~2.4.
@wtfzdotnet I did a quick check and it seems that all unit tests are passing when the version of symfony/event-dispatcher is upgraded to ~3.0. Could you verify that it is safe to upgrade to version 3?

[MarkRedeman]

@Rtransat Is there any reason why you need version 3? I've tested the package with Laravel 5.2 and it seems to work out of the box. Are there other packages that require version 3?

[florentsorel]

I can't check right now but last night composer telling me an error with composer require command about an error with event dispatcher 3.0. It need to install event dispatcher v2 to install the package.

For example, laravel/framework need symfony/http-kernel 2.8 or 3.0 and http-kernel need event-dispatcher ~2.8 or 3.0.

[MarkRedeman]

Then I guess there is some other package that you're using that requires v3.

I've updated PR #25 to change the dependency of event-dispatcher to ~2.8|~3.0, which I will probably merge tonight.

[florentsorel]

It was a fresh install of laravel and php-tmdb/laravel was the first package I've installed in my new laravel installation.

[florentsorel]

I just retry and everything works perfectly, no errors with composer. I don't know why composer throw an error yesterday.

[MarkRedeman]

That's quite weird, maybe someone changed its dependencies?

I've updated PR #25 so that it will be fully compatible with event-dispatcher v3.0.

[MarkRedeman]

@Rtransat I've released a new version that is compatible with v3, so I'm closing this issue.