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

[DI] Make tagged abstract services throw earlier#22420

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
fabpot merged 2 commits intosymfony:masterfromnicolas-grekas:fail-on-abstract
Apr 13, 2017

Conversation

@nicolas-grekas
Copy link
Member

@nicolas-grekasnicolas-grekas commentedApr 13, 2017
edited
Loading

QA
Branch?3.3
Bug fix?yes
New feature?yes
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets-
LicenseMIT
Doc PR-

As spotted by@stof in#22388 (comment), skipping abstract tagged services removes an opportunity to report config mistakes to users.

Instead of skipping them, let's throw as done before (thus reverting#22039, ping@chalasr).
I made$container->findTaggedServiceIds() accept a 2nd arg to make this more systematic.
To keep the possibility to have abstract tagged servicesfor the purpose of tag inheritance,ResolveTagsInheritancePass now resets their tags.

Koc reacted with thumbs up emoji
Copy link
Member

@chalasrchalasr left a comment

Choose a reason for hiding this comment

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

👍

* @return array An array of tags with the tagged service as key, holding a list of attribute arrays
*/
publicfunctionfindTaggedServiceIds($name)
publicfunctionfindTaggedServiceIds($name,$throwOnAbstract =false)
Copy link
Contributor

@KocKocApr 13, 2017
edited
Loading

Choose a reason for hiding this comment

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

what about setnull for now (and consider it asfalse), trigger deprecation warning if no argument value provided (null), change it totrue by default for 4.0?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

this is mostly internal, so not sure it's worth it
but please open a PR if you want to work on it

@fabpot
Copy link
Member

Thank you@nicolas-grekas.

@fabpotfabpot merged commit388e4b3 intosymfony:masterApr 13, 2017
fabpot added a commit that referenced this pull requestApr 13, 2017
…las-grekas)This PR was squashed before being merged into the 3.3-dev branch (closes#22420).Discussion----------[DI] Make tagged abstract services throw earlier| Q             | A| ------------- | ---| Branch?       | 3.3| Bug fix?      | yes| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -As spotted by@stof in#22388 (comment), skipping abstract tagged services removes an opportunity to report config mistakes to users.Instead of skipping them, let's throw as done before (thus reverting#22039, ping@chalasr).I made `$container->findTaggedServiceIds()` accept a 2nd arg to make this more systematic.To keep the possibility to have abstract tagged services *for the purpose of tag inheritance*, `ResolveTagsInheritancePass` now resets their tags.Commits-------388e4b3 [DI] Make tagged abstract services throw earliercd06c12 Revert "minor#22039 Skip abstract definitions in compiler passes (chalasr)"
@nicolas-grekasnicolas-grekas deleted the fail-on-abstract branchApril 13, 2017 15:45
@fabpotfabpot mentioned this pull requestMay 1, 2017
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@stofstofstof approved these changes

@chalasrchalasrchalasr approved these changes

+1 more reviewer

@KocKocKoc left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

3.3

Development

Successfully merging this pull request may close these issues.

6 participants

@nicolas-grekas@fabpot@Koc@stof@chalasr@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp