Movatterモバイル変換


[0]ホーム

URL:


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

Sign up
Appearance settings

Added tip regarding VoterInterface restrictions#2532

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
peterrehm wants to merge3 commits intosymfony:masterfrompeterrehm:patch-2
Closed
Changes fromall commits
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
10 changes: 10 additions & 0 deletionscookbook/security/voters.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -100,6 +100,16 @@ and compare the IP address against a set of blacklisted IP addresses:
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.

.. tip::

Your implementation of the methods
:method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterface::supportsAttribute`
and :method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterface::supportsClass`
are not being called internally by the framework. Once you have registered your
voter the ``vote()`` method will always be called, not depending on your
restrictions. Therefore you need to call those methods in your implementation
of the ``vote()`` method.

Declaring the Voter as a Service
--------------------------------

Expand Down

[8]ページ先頭

©2009-2025 Movatter.jp