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

[FrameworkBundle] Fix misresolved parameters in debug:config#20909

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

@chalasr
Copy link
Member

QA
Branch?3.2
Bug fix?yes
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed ticketsn/a
LicenseMIT
Doc PRn/a

This fixes parameters resolution (classic and env ones) indebug:config, again.
Merging#20714 broke the fix resolving env parameters made in#20688, and anyway it was mismerged (#20714 was not applied when using thepath argument, my bad, I should have prevented it).

This adds a test which prevents regressions so I hope this is is the last PR on this subject.
The buggy output is unfortunately part of the last 3.2 release... It can easily be confirmed by runningdebug:config doctrine on a fresh symfony-demo project

@chalasr
Copy link
MemberAuthor

The patch proposed by fabbot is not related to this PR thus cannot be applied.


privatestaticfunctionresolveParametersValues(ContainerBuilder$builder,$configs)
{
return$builder->resolveEnvPlaceholders($builder->getParameterBag()->resolveValue($configs));

Choose a reason for hiding this comment

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

Not sure about the need for this method

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

I thought it could ease updating this command again after#20618, removed

@nicolas-grekas
Copy link
Member

Why that? I think we can apply it, wouldn't be the first time.

@chalasrchalasrforce-pushed thefix/debug-config-resolve-params branch 3 times, most recently from5f1b505 to1d17ae2CompareDecember 13, 2016 19:07
@chalasr
Copy link
MemberAuthor

From our contributing guidelines:

Never fix coding standards in some existing code as it makes the code review more difficult;

Applied! :)

@nicolas-grekas
Copy link
Member

👍

@chalasrchalasrforce-pushed thefix/debug-config-resolve-params branch from1d17ae2 toc88bc89CompareDecember 13, 2016 19:36
@chalasrchalasr changed the titleFix misresolved parameters in debug:config on 3.2[FrameworkBundle] Fix misresolved parameters in debug:configDec 13, 2016
@fabpot
Copy link
Member

Thank you@chalasr.

@fabpotfabpot merged commitc88bc89 intosymfony:3.2Dec 14, 2016
fabpot added a commit that referenced this pull requestDec 14, 2016
This PR was merged into the 3.2 branch.Discussion----------Fix misresolved parameters in debug:config on 3.2| Q             | A| ------------- | ---| Branch?       | 3.2| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | n/a| License       | MIT| Doc PR        | n/aThis fixes parameters resolution (classic and env ones) in `debug:config`, again.Merging#20714 broke the fix resolving env parameters made in#20688, and anyway it was mismerged (#20714 was not applied when using the `path` argument, my bad, I should have prevented it).This adds a test which prevents regressions so I hope this is is the last PR on this subject.The buggy output is unfortunately part of the last 3.2 release... It can easily be confirmed by running `debug:config doctrine` on a fresh symfony-demo projectCommits-------c88bc89 Fix misresolved parameters in debug:config on 3.2
@chalasrchalasr deleted the fix/debug-config-resolve-params branchDecember 14, 2016 21:49
@fabpotfabpot mentioned this pull requestJan 12, 2017
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas left review comments

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@chalasr@nicolas-grekas@fabpot@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp