From 3189563ce824beb9871f4ef27195eed21a3a07d2 Mon Sep 17 00:00:00 2001 From: Arman Hosseini Date: Sun, 15 Nov 2020 21:48:36 +0330 Subject: [PATCH] Use AppBundle instead of Acme\UserBundle AppBundle is used in all contexts and it is better to keep this name until the end in this branch. --- security/named_encoders.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/security/named_encoders.rst b/security/named_encoders.rst index 803f3d16992..78d3094ebbf 100644 --- a/security/named_encoders.rst +++ b/security/named_encoders.rst @@ -52,7 +52,7 @@ to apply to all instances of a specific class: Another option is to use a "named" encoder and then select which encoder you want to use dynamically. -In the previous example, you've set the ``sha512`` algorithm for ``Acme\UserBundle\Entity\User``. +In the previous example, you've set the ``sha512`` algorithm for ``AppBundle\Entity\User``. This may be secure enough for a regular user, but what if you want your admins to have a stronger algorithm, for example ``bcrypt``. This can be done with named encoders: @@ -113,8 +113,8 @@ to use it, the class must implement The interface requires one method - ``getEncoderName()`` - which should return the name of the encoder to use:: - // src/Acme/UserBundle/Entity/User.php - namespace Acme\UserBundle\Entity; + // src/AppBundle/Entity/User.php + namespace AppBundle\Entity\User; use Symfony\Component\Security\Core\Encoder\EncoderAwareInterface; use Symfony\Component\Security\Core\User\UserInterface;