8000 [PhpUnitBridge] Fixed class_alias() for PHPUnit\Framework\Error\Error by stevegrunwell · Pull Request #38336 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[PhpUnitBridge] Fixed class_alias() for PHPUnit\Framework\Error\Error #38336

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
Sep 29, 2020
Merged

[PhpUnitBridge] Fixed class_alias() for PHPUnit\Framework\Error\Error #38336

merged 1 commit into from
Sep 29, 2020

Conversation

stevegrunwell
Copy link
Contributor
Q A
Branch? 4.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets n/a
License MIT
Doc PR n/a

PHPUnit 6.x removed the PHPUnit_Framework_* classes in favor of PHP namespaces, but one error class did not map the same as the others: PHPUnit_Framework_Error.

Instead of mapping to PHPUnit\Framework\Error in the same way that PHPUnit_Framework_Error_Warning mapped to PHPUnit\Framework\Error\Warning, this base class was replaced with PHPUnit\Framework\Error\Error, so we cannot map it using simple string replacement like its descendants.

PHPUnit 6.x removed the PHPUnit_Framework_* classes in favor of PHP namespaces, but one error class did not map the same as the others: `PHPUnit_Framework_Error`.

Instead of mapping to `PHPUnit\Framework\Error` in the same way that `PHPUnit_Framework_Error_Warning` mapped to `PHPUnit\Framework\Error\Warning`, this base class was replaced with `PHPUnit\Framework\Error\Error`.
@fabpot
Copy link
Member
fabpot commented Sep 29, 2020

Thank you @stevegrunwell.

@fabpot fabpot merged commit 72ff401 into symfony:4.4 Sep 29, 2020
@stevegrunwell stevegrunwell deleted the phpunit-bridge/error-class-aliasing branch September 29, 2020 14:06
This was referenced Oct 4, 2020
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
0