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

[Messenger] Only subscribe to a given bus from the MessageSubscriber#28275

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

Merged
sroze merged 1 commit intosymfony:masterfromsroze:only-subscribe-to-a-given-bus
Aug 28, 2018

Conversation

@sroze
Copy link
Contributor

@srozesroze commentedAug 26, 2018
edited
Loading

QA
Branch?master
Bug fix?no
New feature?yes
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets#...
LicenseMIT
Doc PRø

#27275 introduced the ability to listen to only a few buses from the handler tag. This adds that ability directly from the message subscriber.

It has also highlighted to me that most of the configuration can be done usingyield (like the example I've added in this PR's tests) and that we could remove the support for other ways (especially the obscurereturn [['method', -10]] syntax) but I believe this should be donein another pull-request (that I'm happy to do after this one).

Bernardstanislas and andreybolonin reacted with hooray emoji
Copy link
Member

@nicolas-grekasnicolas-grekas left a comment

Choose a reason for hiding this comment

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

(just wondering: what happens when there's a typo in the bus name? exception for bus not found?)

@srozesrozeforce-pushed theonly-subscribe-to-a-given-bus branch frome27885d tof60e409CompareAugust 27, 2018 11:34
@sroze
Copy link
ContributorAuthor

@nicolas-grekas good point, I've added this scenario in a test 👌

@srozesroze merged commitf60e409 intosymfony:masterAug 28, 2018
sroze added a commit that referenced this pull requestAug 28, 2018
…sageSubscriber (sroze)This PR was merged into the 4.2-dev branch.Discussion----------[Messenger] Only subscribe to a given bus from the MessageSubscriber| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | #...   <!-- #-prefixed issue number(s), if any -->| License       | MIT| Doc PR        | ø#27275 introduced the ability to listen to only a few buses from the handler tag. This adds that ability directly from the message subscriber.It has also highlighted to me that most of the configuration can be done using `yield` (like the example I've added in this PR's tests) and that we could remove the support for other ways (especially the obscure `return [['method', -10]]` syntax) but I believe this should be done **in another pull-request** (that I'm happy to do after this one).Commits-------f60e409 Only subscribe to a given bus from the MessageSubscriber
@srozesroze deleted the only-subscribe-to-a-given-bus branchAugust 28, 2018 12:44
fabpot added a commit that referenced this pull requestAug 29, 2018
…nfiguration (sroze)This PR was merged into the 4.2-dev branch.Discussion----------[Messenger] Remove the "obscure" message subscriber configuration| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | no| BC breaks?    | yes| Deprecations? | no| Tests pass?   | yes| Fixed tickets | ø| License       | MIT| Doc PR        | øAs described in#28275, all of the configuration can be done using yield and that we could remove the support for other ways (especially the obscure return `[['method', -10]]` syntax) as I believe this would clarify the configuration a lot.Commits-------cf2ad86 Remove the "obscure" message subscriber configuration
@nicolas-grekasnicolas-grekas modified the milestones:next,4.2Nov 1, 2018
This was referencedNov 3, 2018
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas approved these changes

@chalasrchalasrchalasr approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

4.2

Development

Successfully merging this pull request may close these issues.

4 participants

@sroze@nicolas-grekas@chalasr@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp