Skip to content

Update setAllowedTypes in Client to use new signature#81

Merged
wtfzdotnet merged 1 commit intophp-tmdb:2.0from
actioussan:FixSymphonyDeprecatedWarning
Jun 21, 2015
Merged

Update setAllowedTypes in Client to use new signature#81
wtfzdotnet merged 1 commit intophp-tmdb:2.0from
actioussan:FixSymphonyDeprecatedWarning

Conversation

@actioussan
Copy link
Copy Markdown
Contributor

OptionsResolver::setAllowedTypes method with an array of options is deprecated since version 2.6 and will be removed in 3.0. Updated to use the new signature with a single option instead.

@wtfzdotnet
Copy link
Copy Markdown
Member

I've made this change before and if I recall correctly it didn't work with the minimal dependency versions as it is, could you verify this? ( composer has a flag to install the least versions possible )

@actioussan
Copy link
Copy Markdown
Contributor Author

You're right, the setAllowedTypes method was first changed in version 2.6, so this change doesn't work for lower versions

@wtfzdotnet
Copy link
Copy Markdown
Member

I'll leave this pull request open as this change will be made at a later date, pushing this through right now might burn some people's camp down :). Thanks for the effort!

@wtfzdotnet wtfzdotnet added this to the Freezer milestone Mar 16, 2015
@wtfzdotnet
Copy link
Copy Markdown
Member

@actioussan any way you could modify this PR to support both versions? I've given it some thought myself and would probably be best moving these two cases into separate classes?

wtfzdotnet added a commit that referenced this pull request Jun 21, 2015
Update setAllowedTypes in Client to use new signature
@wtfzdotnet wtfzdotnet merged commit a151ab9 into php-tmdb:2.0 Jun 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants