Skip to content

NullOutput should be passed to $command->run() #6685

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

Ma27
Copy link
Contributor

@Ma27 Ma27 commented Jun 26, 2016

as $command#execute() is protected, the NullOutput should be passed to $command#run() as that's the public method being invoked when calling an existing command.

as $command#execute() is protected, the NullOutput should be passed to $command#run() as that's the public method being invoked when calling an existing command.
@xabbuh
Copy link
Member

xabbuh commented Jun 26, 2016

👍

Status: Reviewed

@javiereguiluz
Copy link
Member

👍

@xabbuh
Copy link
Member

xabbuh commented Jun 30, 2016

Good catch, thanks Maximilian.

xabbuh added a commit that referenced this pull request Jun 30, 2016
This PR was submitted for the master branch but it was merged into the 2.7 branch instead (closes #6685).

Discussion
----------

NullOutput should be passed to $command->run()

as $command#execute() is protected, the NullOutput should be passed to $command#run() as that's the public method being invoked when calling an existing command.

Commits
-------

5796c81 NullOutput should be passed to $command->run()
@xabbuh xabbuh closed this Jun 30, 2016
@Ma27 Ma27 deleted the patch-1 branch June 30, 2016 16:31
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.

4 participants