Skip to content

Do not trigger deprecation error in ResolveParameterPlaceHoldersPass #14988

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

murnieza
Copy link

Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets none
License MIT
Doc PR none

@@ -38,7 +38,7 @@ public function process(ContainerBuilder $container)
$definition->setFile($parameterBag->resolveValue($definition->getFile()));
$definition->setArguments($parameterBag->resolveValue($definition->getArguments()));
if ($definition->getFactoryClass(false)) {
$definition->setFactoryClass($parameterBag->resolveValue($definition->getFactoryClass()));
$definition->setFactoryClass($parameterBag->resolveValue($definition->getFactoryClass(false)));
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this is no longer required, see #14900.

Copy link
Member

Choose a reason for hiding this comment

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

Yes it is! We still have to trigger the relevant notices, and only them. Silencing can be turned off (and will be by users preparing for 3.0 migration).

@nicolas-grekas
Copy link
Member

I voted too quickly, removing it for now. When this code path is taken, it means one is using a deprecated service factories configuration. Why should we hide the notice? To me, there is something to upgrade, thus to warn about. Did I miss something?

@stof
Copy link
Member

stof commented Jun 15, 2015

@nicolas-grekas but you already got the notice in the place using it. This will trigger a second notice in a place out of the control of the user

@stof
Copy link
Member

stof commented Jun 15, 2015

btw, the call to setFactoryClass will also trigger a deprecation warning here, so you would even get 2 new warnings

@nicolas-grekas
Copy link
Member

@stof true, thanks for the review! 👍 then

@fabpot
Copy link
Member

fabpot commented Jun 15, 2015

Thank you @murnieza.

@fabpot fabpot closed this Jun 15, 2015
fabpot added a commit that referenced this pull request Jun 15, 2015
…eHoldersPass (murnieza)

This PR was submitted for the 2.8 branch but it was merged into the 2.7 branch instead (closes #14988).

Discussion
----------

Do not trigger deprecation error in ResolveParameterPlaceHoldersPass

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |  none
| License       | MIT
| Doc PR        | none

Commits
-------

600078a Do not trigger deprecation error in ResolveParameterPlaceHoldersPass
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants