Skip to content

Commit 3189563

Browse files
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.
1 parent d6203f8 commit 3189563

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

security/named_encoders.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ to apply to all instances of a specific class:
5252
Another option is to use a "named" encoder and then select which encoder
5353
you want to use dynamically.
5454

55-
In the previous example, you've set the ``sha512`` algorithm for ``Acme\UserBundle\Entity\User``.
55+
In the previous example, you've set the ``sha512`` algorithm for ``AppBundle\Entity\User``.
5656
This may be secure enough for a regular user, but what if you want your admins
5757
to have a stronger algorithm, for example ``bcrypt``. This can be done with
5858
named encoders:
@@ -113,8 +113,8 @@ to use it, the class must implement
113113
The interface requires one method - ``getEncoderName()`` - which should return
114114
the name of the encoder to use::
115115

116-
// src/Acme/UserBundle/Entity/User.php
117-
namespace Acme\UserBundle\Entity;
116+
// src/AppBundle/Entity/User.php
117+
namespace AppBundle\Entity\User;
118118

119119
use Symfony\Component\Security\Core\Encoder\EncoderAwareInterface;
120120
use Symfony\Component\Security\Core\User\UserInterface;

0 commit comments

Comments
 (0)