Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 5275230

Browse filesBrowse files
Michael Kleinweaverryan
authored andcommitted
updated with missing fixes
1 parent f4eb5f3 commit 5275230
Copy full SHA for 5275230

File tree

Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed

‎cookbook/security/voters_data_permission.rst

Copy file name to clipboardExpand all lines: cookbook/security/voters_data_permission.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ which has this structure:
3636

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

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

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

145145
Declaring the Voter as a Service
146146
--------------------------------

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.