Skip to content

Commit ed752a3

Browse files
committed
minor symfony#9586 [ExpressionLanguage] Use CacheItemPoolInterface in code example (mheki)
This PR was merged into the 4.0 branch. Discussion ---------- [ExpressionLanguage] Use CacheItemPoolInterface in code example `ParserCacheInterface` was removed in symfony 4.0 in favour of `CacheItemPoolInterface`. This PR updates code example to use currently available interface Commits ------- a81106b Use CacheItemPoolInterface
2 parents e2c8943 + a81106b commit ed752a3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

components/expression_language/extending.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -120,12 +120,12 @@ or by using the second argument of the constructor::
120120
It is recommended to create your own ``ExpressionLanguage`` class in your
121121
library. Now you can add the extension by overriding the constructor::
122122

123+
use Psr\Cache\CacheItemPoolInterface;
123124
use Symfony\Component\ExpressionLanguage\ExpressionLanguage as BaseExpressionLanguage;
124-
use Symfony\Component\ExpressionLanguage\ParserCache\ParserCacheInterface;
125125

126126
class ExpressionLanguage extends BaseExpressionLanguage
127127
{
128-
public function __construct(ParserCacheInterface $parser = null, array $providers = array())
128+
public function __construct(CacheItemPoolInterface $parser = null, array $providers = array())
129129
{
130130
// prepends the default provider to let users override it easily
131131
array_unshift($providers, new StringExpressionLanguageProvider());

0 commit comments

Comments
 (0)