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

Fixed event listeners priority#3719

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

Conversation

tony-co
Copy link
Contributor

QA
Doc fix?yes
New docs?no
Applies toall
Fixed tickets-

from -255 to 255, and the warmers will be executed in the order of their
priority.
The ``priority`` value is optional, and defaults to 0. The core Symfony
listeners priorities varies from -1024 to 1024, and the warmers will be
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

"vary" because it's listener priorities, no?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

indeed

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

and the comma before "and" should be removed

@saro0h
Copy link
Contributor

👍

@wouterj
Copy link
Member

For the next time you submit a fix: If you answer "all" to "Applies to", you should base your PR on the 2.3 branch (since it's the oldest still maintained version). If you answer with a version to "Applies to", it should be based on the branch representing that version (wheremaster is the dev version)

@tony-co
Copy link
ContributorAuthor

@wouterj Ok got it.

@wouterj
Copy link
Member

Actually, this is not true. The core cache warmers are:

One has a priority of20, the other two have a priority of0.

The previous sentence was also not true, there are no limitations of the priority.

@tony-co
Copy link
ContributorAuthor

Indeed.
I was confused by the table just below listing all listeners with their priorities while this phrase is supposed to be only related to cache warmers. Well maybe this phrase should be move out of the cache warmers paragraph and should explain the priority system for all listeners, what do you think@wouterj ?
http://symfony.com/doc/current/reference/dic_tags.html#kernel-event-listener

@wouterj
Copy link
Member

Cache warmers are no listeners.

However, I think we should remove "The core Symfony listeners priorities vary from -1024 to 1024 and the warmers will be executed in the order of their priority." completely. It doesn't make sense and is not really usefull... However, we can add a table like for the listeners showing the 3 core cache warmers and their priority.

@lyrixx
Copy link
Member

We need a sentence that explain "The bigger the priority, the sooner is the execution".

@tony-co
Copy link
ContributorAuthor

Okay, I removed the phrasing and put a quick note about priority along with a table of the three cache warmers.

The higher the priority, the sooner it gets executed.

kernel.cache_warmer
..............
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

this should be something like:

Core Cache Warmers..................

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Sorry about that, it's fixed. I kept the tag name for consistency with the rest of the tables below.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

the rest of the tables below refer to event names, not the tag names. Since cache warmers aren't event, they should not be treated the same

The higher the priority, the sooner it gets executed.

Core Cache Warmers
..................
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This needs to be~~~~~~~~~ here. Small detail, but it's failing on Travis

@weaverryan
Copy link
Member

Nice addition - thanks for the hard work Tony!

weaverryan added a commit that referenced this pull requestApr 2, 2014
This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes#3719).Discussion----------Fixed event listeners priority| Q             | A| ------------- | ---| Doc fix?      | yes| New docs?     | no| Applies to    | all| Fixed tickets | -Commits-------47d4d4f Fixed title level consistency1dbfd29 Updated title for the core cache warmersa9d07a5 Fixed title underline815f531 Replaced the priority paragraph with a note and a tabledb2c002 Fixed event listeners priority (typos after review)13b5645 Fixed event listeners priority
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@tony-co@saro0h@wouterj@lyrixx@weaverryan

[8]ページ先頭

©2009-2025 Movatter.jp