The "PHPUnit\TextUI\ResultPrinter" class is considered internal

[metalfm]

Hello,
Thank you for your package, its awesome!

Can you fix deprecation notice?

my test command

/var/www/html $ bin/phpunit --filter ArraysTest
PHPUnit 8.5.2 by Sebastian Bergmann and contributors.

Testing Project Test Suite

                       App\Tests\Common\ArraysTest ...

Time: 216 ms, Memory: 8.00 MB

OK (3 tests, 6 assertions)

Other deprecation notices (1)

  1x: The "PHPUnit\TextUI\ResultPrinter" class is considered internal This class is not covered by the backward compatibility promise for PHPUnit. It may change without further notice. You should not use it from "DiabloMedia\PHPUnit\Printer\PrettyPrinter".

Symfony version

/var/www/html $ bin/console --version
Symfony 4.4.3 (env: dev, debug: true)

Php version, run in official alpine php docker image

PHP 7.4.0 (cli) (built: Nov 28 2019 21:00:19) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.0, Copyright (c), by Zend Technologies
    with Xdebug v2.8.1, Copyright (c) 2002-2019, by Derick Rethans

[jaydiablo]

This appears to be due to this issue in phpunit: sebastianbergmann/phpunit#3236

I see other result printer libraries with the same issue coming up:

mikeerickson/phpunit-pretty-result-printer#155
indentno/phpunit-pretty-print#28

Based on the discussion in the phpunit issue, it seems like it should be possible to request that the class become part of the public API (and the @internal doc block removed). I'll make a ticket with phpunit to see where that goes.

[jaydiablo]

@metalfm See the issue I filed with PHPUnit: sebastianbergmann/phpunit#4024

There's really nothing we can do at this point, the message you're seeing is from the Symfony PHPUnit bridge apparently and not PHPUnit itself.

When PHPUnit 9.0 is released, we'll have to change this printer a little bit, but I don't think there's anything we can do for PHPUnit 8.0 aside from duplicating all of the code in PHPUnit\TextUI\ResultPrinter so the class isn't extended, which doesn't seem like a great solution.

Is there a way to ignore that notice in the symfony bridge?

[metalfm]

Ok, thank you)