Skip to content

[PHPUnit bridge] Avoid running the remove command without any packages #26170

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

Merged
merged 1 commit into from
Feb 14, 2018

Conversation

stof
Copy link
Member

@stof stof commented Feb 13, 2018

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

As the exit code of the command was not checked, the failure was not breaking things, but it was still printing a confusing error message.
This does not apply to versions older than 3.4, as it was impossible to set SYMFONY_PHPUNIT_REMOVE to an empty string before (it was applying the default removing rules instead in such case)

As the exit code of the command was not checked, the failure was not
breaking things, but it was still printing a confusing error message.
@stof stof changed the title Avoid running the remove command without any packages [PHPUnit bridge] Avoid running the remove command without any packages Feb 13, 2018
@stof stof requested a review from nicolas-grekas February 14, 2018 11:29
@nicolas-grekas nicolas-grekas added this to the 3.4 milestone Feb 14, 2018
@nicolas-grekas
Copy link
Member

Thank you @stof.

@nicolas-grekas nicolas-grekas merged commit 34d2781 into symfony:3.4 Feb 14, 2018
nicolas-grekas added a commit that referenced this pull request Feb 14, 2018
…any packages (stof)

This PR was merged into the 3.4 branch.

Discussion
----------

[PHPUnit bridge] Avoid running the remove command without any packages

| Q             | A
| ------------- | ---
| Branch?       | 3.4
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes/no
| Fixed tickets | n/a
| License       | MIT
| Doc PR        | n/a

As the exit code of the command was not checked, the failure was not breaking things, but it was still printing a confusing error message.
This does not apply to versions older than 3.4, as it was impossible to set `SYMFONY_PHPUNIT_REMOVE` to an empty string before (it was applying the default removing rules instead in such case)

Commits
-------

34d2781 Avoid running the remove command without any packages
@stof stof deleted the fix_no_removal branch February 14, 2018 11:56
This was referenced Mar 1, 2018
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.

3 participants