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 problem is apparent when we go to: \Gigya\GigyaIM\Model\Config::getSessionMode. The docblock indicates that the return type is int. However, there is no type-coercion in place so the docblock is misleading. The \Magento\Framework\App\Config\ScopeConfigInterface::getValue that it directly returns affirms that the return type is actually mixed.
Then, if we go to \Gigya\GigyaIM\Block\GigyaScript::getUserSessionLifetime, we notice that the match statement is based only in integers.
The fix is simple: add (int) to the return of \Gigya\GigyaIM\Model\Config::getSessionMode. OR: add (int) the $mode declaration in \Gigya\GigyaIM\Block\GigyaScript::getUserSessionLifetime.
The text was updated successfully, but these errors were encountered:
Steps to replicate:
gigya/magento2-im
version 6.1.1Uncaught SyntaxError: Unexpected token ','
:sessionExpiration: ,
Background
The problem is apparent when we go to:
\Gigya\GigyaIM\Model\Config::getSessionMode
. The docblock indicates that the return type isint
. However, there is no type-coercion in place so the docblock is misleading. The\Magento\Framework\App\Config\ScopeConfigInterface::getValue
that it directly returns affirms that the return type is actuallymixed
.Then, if we go to
\Gigya\GigyaIM\Block\GigyaScript::getUserSessionLifetime
, we notice that thematch
statement is based only in integers.The fix is simple: add
(int)
to the return of\Gigya\GigyaIM\Model\Config::getSessionMode
. OR: add(int)
the$mode
declaration in\Gigya\GigyaIM\Block\GigyaScript::getUserSessionLifetime
.The text was updated successfully, but these errors were encountered: