Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Nov 4, 2015

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

Now that we deprecated the ContainerAware class in #16424 I think we should do the same with the ContainerAwareCommand class.

@stof
Copy link
Member

stof commented Nov 4, 2015

-1 for this, because this command does more than what the trait does

@nicolas-grekas
Copy link
Member

the logic in getContainer looks unique so I agree with @stof
but in 3.0, the trait could be used to remove setContainer (which could be done in #16411)

@stof
Copy link
Member

stof commented Nov 4, 2015

@nicolas-grekas using the trait would make the container property protected (which is why it was removed from the PR btw)

@Tobion
Copy link
Contributor

Tobion commented Nov 4, 2015

I didn't include this in #16411 for exactly the two reasons given by stof. So -1
The container property should not be protected because it would allow subclasses to use the property instead of the protected getter, which is supposed to be used.

@xabbuh xabbuh closed this Nov 4, 2015
@xabbuh xabbuh deleted the deprecate-container-aware-command branch November 4, 2015 18:38
@xabbuh
Copy link
Member Author

xabbuh commented Nov 4, 2015

You are right. The logic in getContainer() is actually different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants