- 
                Notifications
    You must be signed in to change notification settings 
- Fork 2.6k
Avoid triggering a deprecation notice in doctrine/collections #12238
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
Conversation
| @greg0ire Please advise: Should I bump requirements for doctrine/collections in composer.json here? I guess I cannot, since we're still compatible with  | 
60148e0    to
    0060f4d      
    Compare
  
    This updates the code to avoid triggering the deprecation introduced in doctrine/collections#472.
0060f4d    to
    1865717      
    Compare
  
    | That's right, you shouldn't. Not in a patch release anyway. | 
| Found doctrine/doctrine-website#485. I knew we discussed that before. So, how to make PHPStan happy when I cannot tell for sure if checking against doctrine/collections >= 2.4.0 or below that? | 
| What do you mean? The CI job is installing  | 
f87e380    to
    da67f32      
    Compare
  
    | Thanks @mpdude ! | 
This updates the code to avoid triggering the deprecation introduced in doctrine/collections#472.
Closes #12237.