-
Notifications
You must be signed in to change notification settings - Fork 59
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
[BUG]Deprecate implicitly nullable parameter type in ringphp #242
Comments
There's a PR in progress in #233 to get rid of ringphp, any help there would be appreciated. |
I think it’s a great initiative to move away from ringphp. However, I believe it could be a challenging and time-consuming effort. Do you have any temporary solutions or workarounds in mind? |
AFAIK there aren't any |
@dblock It seems it is blocker to upgrade PHP 8.4 So, Are we working on any workaround or any discussion in progress regarding the same to mitigate this? |
There are no workarounds for this AFAIK, so #233 is it. |
The change "Deprecate implicitly nullable parameter types" was introduced in PHP 8.4. This means that if a parameter's default value is set to null, its type declaration must explicitly include null or be nullable using a union type.
This issue also exists in the ezimuel/ringphp library that this project depends on. However, ezimuel/ringphp appears to be inactive, as it is a fork of the original library.
How should we address this situation?
ezimuel/ringphp#13
The text was updated successfully, but these errors were encountered: