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] Fix tracking of env vars in exceptions#25163

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

Conversation

@nicolas-grekas
Copy link
Member

@nicolas-grekasnicolas-grekas commentedNov 26, 2017
edited
Loading

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

Fixes the bad exception message reported in the linked issue (regression introduced in v3.3.7).

Best reviewedignoring whitespaces.

$tmpContainer =newContainerBuilder($resolvingBag);
$tmpContainer->setResourceTracking($container->isTrackingResources());
$tmpContainer->addObjectResource($extension);
if ($extensioninstanceof ConfigurationExtensionInterface &&null !==$configuration =$extension->getConfiguration($config,$tmpContainer)) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Assignment in condition?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Indeed :) Was here before, and not forbidden by our policy, you can find many others in the code base.


$extension->load($config,$tmpContainer);
$extension->load($config,$tmpContainer);
}catch (\Exception$e) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Any chance to specify less general exception?

Copy link
MemberAuthor

@nicolas-grekasnicolas-grekasNov 26, 2017
edited
Loading

Choose a reason for hiding this comment

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

Would be a bug.Could be "finally" in fact.

@nicolas-grekasnicolas-grekas merged commit73f1ac5 intosymfony:3.3Nov 27, 2017
nicolas-grekas added a commit that referenced this pull requestNov 27, 2017
This PR was merged into the 3.3 branch.Discussion----------[DI] Fix tracking of env vars in exceptions| Q             | A| ------------- | ---| Branch?       | 3.3| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#24270,#24368| License       | MIT| Doc PR        | -Fixes the bad exception message reported in the linked issue (regression introduced in v3.3.7).Best reviewed [ignoring whitespaces](https://github.com/symfony/symfony/pull/25163/files?w=1).Commits-------73f1ac5 [DI] Fix tracking of env vars in exceptions
@nicolas-grekasnicolas-grekas deleted the di-merge-env-exceptions branchNovember 27, 2017 09:52
This was referencedNov 30, 2017
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

1 more reviewer

@SCIFSCIFSCIF 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.

3 participants

@nicolas-grekas@SCIF@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp