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.

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

[EventDispatcher] Fix hardcoded listenerTag name in error message #9940

Conversation

lemoinem
Copy link
Contributor

@lemoinem lemoinem commented Jan 4, 2014

Q A
Fixed tickets N/A
License MIT

Just as the title say, there was a kernel.event_listener string hardcoded in an error message although everywhere else in this class it is stored in the $listenerTag property.

fabpot added a commit that referenced this pull request Jan 5, 2014
…essage (lemoinem)

This PR was submitted for the 2.3-dev branch but it was merged into the 2.3 branch instead (closes #9940).

Discussion
----------

[EventDispatcher] Fix hardcoded listenerTag name in error message

| Q             | A
| ------------- | ---
| Fixed tickets | N/A
| License       | MIT

Just as the title say, there was a kernel.event_listener string hardcoded in an error message although everywhere else in this class it is stored in the `$listenerTag` property.

Commits
-------

8c91537 [EventDispatcher] Fix hardcoded listenerTag name in error message
@fabpot fabpot closed this Jan 5, 2014
@lemoinem lemoinem deleted the fix/harcoded-message-in-RegisterListenersPass branch January 6, 2014 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants