-
Having to require PEAR as a repository kills the performance of Composer package updates, and we are only using a small subset of the functionality. We should evaluate whether rolling our own thing wo…
-
At the end of an inspection, I'm not always receiving an e-mail.
With open-source projects hosted on Github, everything is running smoothly. At the end of an inspection, I get a mail.
With closed-so…
-
When using a class which implements a magic method (e.g. __call()), the class should contain @method documentation describing on which methods are available on the object.
This works, but only on the …
-
Code needs some refactoring:
- [ ] reformat - could be done through clang-format, would be great if reformat would be done automatically before each commit (as git hook) or available as run script
-…
-
Consider this case: https://scrutinizer-ci.com/g/morrisonlevi/Ardent/indices/119906/duplications/577766
Essentially it looks like this:
``` php
public function map(callable $map) {
$structure = …
-
Would be nice to have badges and Travis or public CI + Coverage
-
Currently, the code coverage UI displays the coverage ratio for classes and the CRAP score for methods.
While having the CRAP score is a good idea, it would be good to have the ratio as well for metho…
stof updated
10 years ago
-
Trust in data quality is key and ideally there is a general way at least for all contributing datasets to the CoL to indicate if an individual record has been reviewed by an expert. Questions to be ad…
-
Currently there are a few instances of code generation:
**Class generators**
- Generating specs on `describe`
- Generating classes when class does not exit
**Class modifiers**
- Generating methods t…
-
Hi,
Imo the current class scoring is irrelevant. If the complexity makes sense for functions, it makes not sense for classes the way it's done by scrutinizer.
Classes score should be evaluated on ho…
jails updated
9 years ago