Commits on Jan 6, 2017
If a function call is made to set the value of a constant through `define()`, it depends on the function called whether or not the value passed to `define()` is one of the acceptable variable types, but determining what the variable type returned by the function call is (or could be), is outside of the scope of a static analyse tool. So I believe, in that case we should not throw an error. Includes additional unit tests. Also changes the `testVersion` for the `noViolation` / false positives test to `5.6` to prevet interference from the short array syntax sniff.
Commits on Jan 4, 2017
Commits on Jan 3, 2017
This seemed like a quick fix to make. In PHPCS 2.3.4 - 2.5.2, this sniff would throw an error about the `T_ANON_CLASS` constant not being defined (as it wasn't fully implemented properly in PHPCS until PHPCS 2.6.0). Pre-PHPCS 2.3.4, the sniff was disregarded and the test skipped. Includes additional test against false positives (test case was already in place, just not tested). Removes test exclusion for this sniff on PHPCS <2.3.4.
Commits on Jan 1, 2017
Includes additional unit tests.