Skip to content

Commit e2c2e19

Browse files
asandjivyxabbuh
authored andcommitted
Update entity_provider.rst
1 parent 748b3e9 commit e2c2e19

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

security/entity_provider.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -561,10 +561,10 @@ above). This gives us a "fresh" User object.
561561
But Symfony also uses the ``username``, ``salt``, and ``password`` to verify
562562
that the User has not changed between requests (it also calls your ``AdvancedUserInterface``
563563
methods if you implement it). Failing to serialize these may cause you to
564-
be logged out on each request. If your User implements the
564+
be logged out on each request. If your user implements the
565565
:class:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface`,
566-
then instead of these properties being checked, your ``isEqualTo`` method
567-
is simply called, and you can check whatever properties you want. Unless
566+
then instead of these properties being checked, your :method:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface::isEqualTo` method
567+
is called, and you can check whatever properties you want. Unless
568568
you understand this, you probably *won't* need to implement this interface
569569
or worry about it.
570570

0 commit comments

Comments
 (0)