8000 New Data Voter Article (continuation) by weaverryan · Pull Request #3594 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

New Data Voter Article (continuation) #3594

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.

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

Merged
merged 15 commits into from
Mar 4, 2014
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
updated with missing fixes
  • Loading branch information
Michael Klein authored and weaverryan committed Feb 20, 2014
commit 52752309eb2472a0563e395c369700fac6c7e5ca
4 changes: 2 additions & 2 deletions cookbook/security/voters_data_permission.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ which has this structure:

.. include:: /cookbook/security/voter_interface.rst.inc

In this example, you'll check if the user will have access to a specific
In this example, it'll check if the user will have access to a specific
object according to your custom conditions (e.g. he must be the owner of
the object). If the condition fails, you'll return
``VoterInterface::ACCESS_DENIED``, otherwise you'll return
Expand Down Expand Up @@ -140,7 +140,7 @@ You could store your Voter to check permission for the view and edit action like
}

That's it! The voter is done. The next step is to inject the voter into
the security layer. This can be done easily through the service container.
the security layer.

Declaring the Voter as a Service
--------------------------------
Expand Down
0