-
Notifications
You must be signed in to change notification settings - Fork 51
Conversation
ed41afc
to
ae894c1
Compare
I'm going to redo this branch a bit:
|
Illustrative example: https://gist.github.com/ockham/bffdf72507facf56c328 |
Based on latest experiments, this is proably going toward just having one individual visitor for each check after all, without inheriting from intermediate classes like |
5c1476c
to
84579d1
Compare
167bf1c
to
abe33d1
Compare
d4dd690
to
b05879d
Compare
@stevegrunwell I thought you might be interested in this PR as it's supposed to tighten detection of forbidden patterns vs false positives by using an actual PHP parser instead of fiddling with regexes. Feel free to leave your comments; also see my other (related, leaner) PRs. |
9b5f2ee
to
0bcaee5
Compare
c5a6b1c
to
387c795
Compare
Moved logic from |
Hrm, tests failing with PHP 5.3. I'll fix that as soon as I can. |
Converts Analyzer to PHP parser. Lays the groundwork for converting tests to PHP-Parser (See #218 ) Automattic/vip-quickstart@8c48dc3 Should make it so that Quickstart works with the sub modules this needs.
387c795
to
7ef01b2
Compare
…stomize_Control classes
d655001
to
24db3a1
Compare
This is another preview PR related to #195. This one is currently based on the other PHP-Parser PR, #204, so what's interesting is the diff between them.
Update 2014-12-20: List of checks mentioned in config-vip-scanner.php, with converted ones checked (modulo some slight general refactoring of
CodeCheckBase
) Note that some checks are for HTML, CSS or JavaScript and cannot be migrated to PHP-Parser.