-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Deprecated class on TwigBundle #16872
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
Comments
It looks like the error report from sensio labs insight is wrong. The |
Hi Tobias,
Many thanks for your tip. I'm going to open a ticket, as you have suggested.
Cheers,
|
Hey, Just to keep you up to date: this is the SensioLabs Insight answer about this case I posted here: Hello David, Removing this violation programmatically is not really possible, as we can't determine in an automatic way if this service is a vendor one or yours. But you can easily just ignore the violation. Best regards, |
If you really want to get rid of it you could overwrite the service. Tested and works with SensioLabsInsight Eg: services.yml services:
# Nullify this service. It is deprecated and raises an error on SensioLabs Insight
twig.extension.actions:
class: AppBundle\Twig\NullExtension AppBundle\Twig\NullExtension.php <?php
namespace AppBundle\Twig;
class NullExtension implements \Twig_ExtensionInterface
{
/**
* {@inheritdoc}
*/
public function initRuntime(\Twig_Environment $environment)
{}
/**
* {@inheritdoc}
*/
public function getTokenParsers()
{
return [];
}
/**
* {@inheritdoc}
*/
public function getNodeVisitors()
{
return [];
}
/**
* {@inheritdoc}
*/
public function getFilters()
{
return [];
}
/**
* {@inheritdoc}
*/
public function getTests()
{
return [];
}
/**
* {@inheritdoc}
*/
public function getFunctions()
{
return [];
}
/**
* {@inheritdoc}
*/
public function getOperators()
{
return [];
}
/**
* {@inheritdoc}
*/
public function getGlobals()
{
return [];
}
/**
* {@inheritdoc}
*/
public function getName()
{
return 'null_extension';
}
} |
Hi Tom, Many thanks for your message. Cheers, |
Hello,
I have been updating my vendors recently, and SensioLabs Insight has reported me that there is 1 deprecated class on
TwigBundle
. Given this is an updated vendor, I presume (from my humble point of vire) it should not be tagged as@deprecated
or it should not be checked on SensioLabs Insight if that class will be removed on next TwigBundle release.This is the error reported by SensioLabs Insight:
Cheers,
The text was updated successfully, but these errors were encountered: