We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. Here #7220 we started adding the support of php8.4 in phpstan and fixed some deprecation errors related to: https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated
And we managed to update action scheduler to 3.9.1 which fixed all the deprecation errors from their side.
And I'm opening this issue as a follow-up to do the same with league container and mobile detect libraries.
Describe the solution you'd like We'd need to check which version of those packages fix this error and discuss about this update and consequences.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
Here #7220 we started adding the support of php8.4 in phpstan and fixed some deprecation errors related to:
https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated
And we managed to update action scheduler to 3.9.1 which fixed all the deprecation errors from their side.
And I'm opening this issue as a follow-up to do the same with league container and mobile detect libraries.
Describe the solution you'd like
We'd need to check which version of those packages fix this error and discuss about this update and consequences.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: