You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently working on PHP 8.4 supports (release ETA November 21st, 2024) and found the following deprecation errors when trying to update laravel/vonage-notification-channel
Expected Behavior
Supports PHP 8.4
Current Behavior
1) /home/runner/work/vonage-notification-channel/vonage-notification-channel/vendor/vonage/client-core/src/Client.php:234
{closure:Vonage\Client::__construct():234}(): Implicitly marking parameter $errfile as nullable is deprecated, the explicit nullable type must be used instead
Triggered by:
* Illuminate\Notifications\Tests\Unit\Channels\VonageSmsChannelTest::testSmsIsSentViaVonage
/home/runner/work/vonage-notification-channel/vonage-notification-channel/tests/Unit/Channels/VonageSmsChannelTest.php:20
2) /home/runner/work/vonage-notification-channel/vonage-notification-channel/vendor/vonage/client-core/src/Client.php:0
{closure:Vonage\Client::__construct():234}(): Implicitly marking parameter $errline as nullable is deprecated, the explicit nullable type must be used instead
Triggered by:
* Illuminate\Notifications\Tests\Unit\Channels\VonageSmsChannelTest::testSmsIsSentViaVonage
/home/runner/work/vonage-notification-channel/vonage-notification-channel/tests/Unit/Channels/VonageSmsChannelTest.php:20
3) /home/runner/work/vonage-notification-channel/vonage-notification-channel/vendor/vonage/client-core/src/Client.php:0
{closure:Vonage\Client::__construct():234}(): Implicitly marking parameter $errorcontext as nullable is deprecated, the explicit nullable type must be used instead
The text was updated successfully, but these errors were encountered:
We are currently working on PHP 8.4 supports (release ETA November 21st, 2024) and found the following deprecation errors when trying to update
laravel/vonage-notification-channel
Expected Behavior
Supports PHP 8.4
Current Behavior
The text was updated successfully, but these errors were encountered: