Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update entity_provider.rst #6893

Closed
wants to merge 2 commits into from
Closed

Update entity_provider.rst #6893

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
47d41d3
Update entity_provider.rst
asandjivy Aug 19, 2016
70a8d55
Update entity_provider.rst
asandjivy Aug 31, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions security/entity_provider.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -533,10 +533,10 @@ above). This gives us a "fresh" User object.
But Symfony also uses the ``username``, ``salt``, and ``password`` to verify
that the User has not changed between requests (it also calls your ``AdvancedUserInterface``
methods if you implement it). Failing to serialize these may cause you to
be logged out on each request. If your User implements the
be logged out on each request. If your user implements the
:class:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface`,
then instead of these properties being checked, your ``isEqualTo`` method
is simply called, and you can check whatever properties you want. Unless
then instead of these properties being checked, your :method:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface::isEqualTo` method
is called, and you can check whatever properties you want. Unless
you understand this, you probably *won't* need to implement this interface
or worry about it.

Expand Down