A new command to validate json config file

The Reflect Command-Line Interface always needs a file in JSON format to run. It should be found either in the current, $HOME/.config/, or /etc directory.

By setting the REFLECT environment variable it is possible to set the filename of phpreflect.json to something else.

E.g: REFLECT=my-phpreflect.json

It’s very usefull to validate structure of the json configuration file before to run any command of Reflect

Example 1. Just run the command below
$ phpreflect validate
Published by Laurent Laville on 2014-07-28

Reflect 2.2.0 has just been released.

Changes :

  • toArray() method was removed and replaced by new render() method in AnalyserInterface.

  • fixed error message on analyser:list command when none analysers defined in json config file.

  • Structure analyser follow now the plug-and-play system. Check if installed (see json config file) before to use it.

  • analyser:run command delegated results render to each analyser via the new render() method of AnalyserInterface.

  • add getStartLine(), getEndLine(), getNamespaceName(), getArguments(), isClassMethod(), isInternalFunction() methods on DependencyModel.

  • add getTypeHint() method on ParameterModel.

  • can now detect direct method call reported as a DependencyModel. Usefull for CompatInfo issue GH-100.

  • can now detect multiple internal function signatures.

  • ability to use cache plugin in other SAPI than CLI.

  • a full documentation for all audiences to read it online or offline.

Alternatively, you may use Composer and install it via Packagist.

Published by Laurent Laville on 2014-07-24

Reflect 2.1.0 has just been released.

Changes :

  • new getClassName() method in the Reflect\Model\PropertyModel to solve PHP CompatInfo GH-119 issue.

  • a full documentation for all audiences.

What is planned for the next version 2.2.0:
  • Implement the cache plugin to speed up later uses.

Alternatively, you may use Composer and install it via Packagist.

Published by Laurent Laville on 2014-07-04

Release 2.1.0 planned

The second release of major branch 2 is planned for Friday July 4, 2014.

It will include a new full documentation for all audiences (basic users and developers).

Published by Laurent Laville on 2014-07-01