Skip to content

Latest commit

 

History

History
31 lines (26 loc) · 2.58 KB

upgrading.md

File metadata and controls

31 lines (26 loc) · 2.58 KB
Raw

Upgrading

The change from previous versions to 9.0 is quite significant but should be really smooth for the user. The main changes are:

  • Cache system used now the symfony/cache component and must be PSR-6 compatible.
  • JUnit XML output did not use anymore the n98/junit-xml dependency. Replaced by a native DOMDocument implementation.
  • --json option was renamed to --log-json
  • --xml option was renamed to --log-junit
  • php://stdout alias to write results stream to standard output is automagically applied (default) when invoking phplint with log-json or log-xml options.
  • Progress display has comestic evolved.
  • New option --progress added to version 9.0 to be able to change progress display (default printer mode is legacy behavior).

For Developers (read also the Architecture Guide)

  • API: Overtrue\PHPLint\Finder is the central point to identify files to scan and use the symfony/finder component.
  • API: Overtrue\PHPLint\Extension\ProgressPrinter replace the Linter process callback (see Overtrue\PHPLint\Linter::setProcessCallback).
  • API: Overtrue\PHPLint\Extension\ProgressBar use the symfony/console progressBar helper
  • API: Overtrue\PHPLint\Output\JsonOutput allow to log scan results in JSON format to file or standard output.
  • API: Overtrue\PHPLint\Output\JunitOutput allow to log scan results in JUnit XML format to file or standard output.
  • API: Overtrue\PHPLint\Event\EventDispatcher is the central point of event listener system and use the symfony/event-dispatcher component.
  • API: Overtrue\PHPLint\Configuration\ConsoleOptionsResolver is the configuration resolver for console CLI usage without YAML file and use the symfony/options-resolver component.
  • API: Overtrue\PHPLint\Configuration\FileOptionsResolver is the configuration resolver for YAML file and use the symfony/options-resolver component.