for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
/*
* This file is part of the Sylius package.
*
* (c) Paweł Jędrzejewski
* For the full copyright and license information, please view the LICENSE
* file that was distributed with this source code.
*/
namespace Sylius\Bundle\AdminBundle\Twig;
/**
* @author Jan Góralski <[email protected]>
final class NotificationWidgetExtension extends \Twig_Extension
{
* @var bool
private $areNotificationsEnabled;
* @var int
private $checkFrequency;
* @param bool $areNotificationsEnabled
* @param int $checkFrequency
public function __construct($areNotificationsEnabled, $checkFrequency)
$areNotificationsEnabled
20
Very long variable names usually make code harder to read. It is therefore recommended not to make variable names too verbose.
$this->areNotificationsEnabled = $areNotificationsEnabled;
$this->checkFrequency = $checkFrequency;
}
* @return array
\Twig_SimpleFunction[]
This check looks for the generic type array as a return type and suggests a more specific type. This type is inferred from the actual code.
array
public function getFunctions()
return [
new \Twig_SimpleFunction(
'sylius_render_notifications_widget',
[$this, 'renderWidget'],
[
'needs_environment' => true,
'is_safe' => ['html'],
]
),
];
* @param \Twig_Environment $environment
* @return string
public function renderWidget(\Twig_Environment $environment)
if (!$this->areNotificationsEnabled) {
return '';
return $environment->render('@SyliusAdmin/_notification.html.twig', [
'frequency' => $this->checkFrequency,
]);
pamil /
Sylius
Loading history...
Very long variable names usually make code harder to read. It is therefore recommended not to make variable names too verbose.