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

Jump to bottom

Fixed build error 'WARNING: undefined label: event_dispatcher' #180

Merged
merged 1 commit into from
Apr 1, 2013
Merged

Fixed build error 'WARNING: undefined label: event_dispatcher' #180

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 4 additions & 3 deletions Resources/doc/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -664,9 +664,10 @@ and then :ref:`tagging<book-service-container-tags>` it with a specific tag.

The ``priority`` attribute, which defaults to ``0`` if omitted, may be used
to control the order that listeners are registered. Much like Symfony2's
:ref:`event dispatcher<event_dispatcher>`, greater numbers will result in
the listener executing first and listeners with the same priority will be
executed in the order that they were registered with the event manager.
:doc:`event dispatcher</components/event_dispatcher/introduction>`, greater
numbers will result in the listener executing first and listeners with the
same priority will be executed in the order that they were registered with
the event manager.

Lastly, the ``lazy`` attribute, which defaults to ``false`` if omitted, may
be used to request that the listener be lazily loaded by the event manager
Expand Down