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] highlight suspicious tests#31942

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

@nicolas-grekas
Copy link
Member

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

Why doesn't this break something?
Related to#27710 I think
/cc@xabbuh@ro0NL if you have any idea why :)

{
publicfunctiongetConfigTreeBuilder()
{
thrownew \Exception();
Copy link
Contributor

Choose a reason for hiding this comment

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

the test ensures we dont require a node to be present, if the user didnt configure anything. However the side effect is the config tree isnt even initialized ... so it doesnt matter much what happens here.

I'd keep this tree for the purpose of clarity, in the sense we don't expect anInvalidConfigException duenodes being required.

{
publicfunctiongetConfigTreeBuilder()
{
thrownew \Exception();
Copy link
Contributor

Choose a reason for hiding this comment

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

this test from#27472 is actually invalidated due#27710, we should pass some config to ensure the treebuilder is called

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

up for a PR?

@ro0NLro0NL mentioned this pull requestJun 7, 2019
@nicolas-grekas
Copy link
MemberAuthor

Closing in favor of#31944, thanks@ro0NL

@nicolas-grekasnicolas-grekas deleted the di-bad-test branchJune 7, 2019 21:07
nicolas-grekas added a commit that referenced this pull requestJun 8, 2019
This PR was merged into the 4.2 branch.Discussion----------[DI] Fix suspicious test| Q             | A| ------------- | ---| Branch?       | 4.2| Bug fix?      | yes| New feature?  | no| BC breaks?    | no     <!-- seehttps://symfony.com/bc -->| Deprecations? | no| Tests pass?   | yes    <!-- please add some, will be required by reviewers -->| Fixed tickets |#31942| License       | MIT| Doc PR        | symfony/symfony-docs#... <!-- required for new features -->cc@nicolas-grekasCommits-------25b961a [DI] Fix suspicious test
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

1 more reviewer

@ro0NLro0NLro0NL left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

4.2

Development

Successfully merging this pull request may close these issues.

3 participants

@nicolas-grekas@ro0NL@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp