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
The Apideck\Client\Model\GetConnectionsResponse methods implementing ArrayAccess PHP interface are not compatible with this interface, making PHP noticing us with a deprecated log:
Return type of Apideck\Client\Model\GetConnectionsResponse::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
As mentioned by PHP, arguments and return types are missing in these implementations:
PHPStan hint:
Fixed version:
⚠️About the fixed version⚠️
The fix I provided is not compatible with PHP ^7.3, which is a version supported by your PHP ApiDeck library (mixed pseudo type was added in PHP 8.0).
Also, PHP versions 7.3 to 8.0 are not supported anymore, maybe it will be time to bump this package version to a new major one introducing this breaking change? I let you think about the strategy 😄
Ping me if you need something else, I'll be happy to help.
The text was updated successfully, but these errors were encountered:
Hi,
The
Apideck\Client\Model\GetConnectionsResponse
methods implementing ArrayAccess PHP interface are not compatible with this interface, making PHP noticing us with a deprecated log:🐞 Debugging informations
File:
/var/www/html/vendor/apideck-libraries/php-sdk/src/gen/lib/Model/GetConnectionsResponse.php
Line:
319
Error level:
8192
As mentioned by PHP, arguments and return types are missing in these implementations:
PHPStan hint:
Fixed version:
The fix I provided is not compatible with PHP ^7.3, which is a version supported by your PHP ApiDeck library (
mixed
pseudo type was added in PHP 8.0).Also, PHP versions 7.3 to 8.0 are not supported anymore, maybe it will be time to bump this package version to a new major one introducing this breaking change? I let you think about the strategy 😄
Ping me if you need something else, I'll be happy to help.
The text was updated successfully, but these errors were encountered: