From 874c84000eb6df47777c916d37cff299140ee26b Mon Sep 17 00:00:00 2001 From: Evgenij Efimov Date: Mon, 4 Jan 2016 22:54:12 +0300 Subject: [PATCH] Removed deprecated methods from VoterInterface --- components/security/authorization.rst | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/components/security/authorization.rst b/components/security/authorization.rst index eb24034b1e5..5306a3eec61 100644 --- a/components/security/authorization.rst +++ b/components/security/authorization.rst @@ -85,25 +85,12 @@ of :class:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterf which means they have to implement a few methods which allows the decision manager to use them: -``supportsAttribute($attribute)`` (deprecated as of 2.8) - will be used to check if the voter knows how to handle the given attribute; - -``supportsClass($class)`` (deprecated as of 2.8) - will be used to check if the voter is able to grant or deny access for - an object of the given class; - ``vote(TokenInterface $token, $object, array $attributes)`` this method will do the actual voting and return a value equal to one of the class constants of :class:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterface`, i.e. ``VoterInterface::ACCESS_GRANTED``, ``VoterInterface::ACCESS_DENIED`` or ``VoterInterface::ACCESS_ABSTAIN``; -.. note:: - - The ``supportsAttribute()`` and ``supportsClass()`` methods are deprecated - as of Symfony 2.8 and no longer required in 3.0. These methods should not - be called outside the voter class. - The Security component contains some standard voters which cover many use cases: