Reflect 3.0.0-alpha-3 has just been released.
3.0.0-alpha3 is a new major milestone of API 3.0
We have reached a point where API is enough stabilized to be the last of alpha state.
All specific code to CompatInfo have been transfered to this project. That includes,
compatinfo.sqlitethe SQLite references database, and the
NodeProcessorcomponent was added to allow individual
NodeVisitorto check pre-conditions before traversing AST.
A new component called
AnalyserManagerwas added to handle more easily each analyser.
Time and Memory usage are always print as soon as
--profileoption is specified. Does not required anymore the
Reflect 3.0.0-alpha-2 has just been released.
3.0.0-alpha2 is a major milestone of new API 3.
Source code is now available on branch 3.0
Here are changes since 3.0.0-alpha1, and of course what’s are changed since 2.6
Ability to provide a file or a directory in command line, without to specify it in
phpreflect.jsonconfig file.Example 1: analyse a full directory (recursivly) without any exclusion$ php phpreflect.phar analyser:run /path/to/dirExample 2: analyse a single file (accept
.php)$ php phpreflect.phar analyser:run /path/to/fileExample 3: analyse a single archive file (
.phar)$ php phpreflect.phar analyser:run /path/to/archiveExample 4: with notification of analysis. Different render with verbose level (
-v|vv|vvv) or none.$ php phpreflect.phar --progress analyser:run /path/to/data/sourceIf you want to limit analysis perimeter, you can do it as in version 2.6 with a
phpreflect.jsonis no more mandatory.
locto count line of codes.
Ability to write CLI result to file or URL (E.g: FTP) with the
--outputoption. Don’t forget the
--no-ansioption.Example 1: writes analysis results to a local file$ php phpreflect.phar --out=/path/to/output_file --no-ansi analyser:run /path/to/data/sourceIf your console support color, do not forget the
--no-ansito remove color escape codes.Example 2: writes analysis results to a remote file$ php phpreflect.phar --out=ftp://user:pass@hostname/path/to/output_file --no-ansi analyser:run /path/to/data/source