[EventDispatcher] Allow to omit the event name when registering listene…

[nicolas-grekas]

Q	A
Feature PR	symfony/symfony#33851
PR author(s)	@derrabus
Merged in	4.4

[derrabus]

I'll write the documentation probably tomorrow.

[carsonbot]

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

[derrabus]

I completely forgot about this one. 🙈

[carsonbot]

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

[carsonbot]

Could I get a reply or should I close this?

[derrabus]

Still relevant, I suppose.

[alamirault]

This was introduce in 4.4, I think is now a good practice to use FQCN instead declare event: kernel.exception.

https://symfony.com/doc/current/components/event_dispatcher.html

https://symfony.com/doc/current/event_dispatcher.html

Are you ok if I do theses changes ? I will add a note below

symfony-docs/event_dispatcher.rst

Lines 127 to 135 in db74d6d

	.. note::
	There is an optional attribute for the ``kernel.event_listener`` tag called
	``priority``, which is a positive or negative integer that defaults to ``0``
	and it controls the order in which listeners are executed (the higher the
	number, the earlier a listener is executed). This is useful when you need to
	guarantee that one listener is executed before another. The priorities of the
	internal Symfony listeners usually range from ``-256`` to ``256`` but your
	own listeners can use any positive or negative integer.