Skip to content

Fix priority range values for event listeners. #5194

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

Closed
wants to merge 3 commits into from
Closed

Fix priority range values for event listeners. #5194

wants to merge 3 commits into from

Conversation

chtipepere
Copy link

According to http://symfony.com/doc/master/reference/dic_tags.html, priority range is from -1024 to +1024.

@wouterj
Copy link
Member

wouterj commented Apr 21, 2015

I think we should remove the range in this section, as you can use whatever number you want. It doesn't limit you to a specific range. The core listeners are within the [-1024 ... 1024] range, but that doesn't have to say anything about your own listeners.

@wouterj
Copy link
Member

wouterj commented Apr 26, 2015

And your first doc contribution is now merged! Congratulations and thanks for submitting it. You'll get the "doc contributor" in some days :) Btw, a little tip for the next time: We don't get updates about new commits that are added to PRs. We'll notice updates quicker if you comment after it (which are notified to the repo followers).

wouterj added a commit that referenced this pull request Apr 26, 2015
This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #5194).

Discussion
----------

Fix priority range values for event listeners.

According to http://symfony.com/doc/master/reference/dic_tags.html, priority range is from -1024 to +1024.

Commits
-------

2492952 Fix priority range values for event listeners.
@wouterj wouterj closed this Apr 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants