Popular posts

I use phpstorm as well for a lot of things, but I have diverse team and I go by the rule of "everything that can be automated should be automated" so relying only on intellij doesn't help me with an atom or sublime user or a VI / Emacs person.

So I need standardized accessible metrics preferable in a pre-commit hook and linting is a good start, but still not enough.

I personally want to have something along the lines of phpmetrics.org/report/latest/index.html

or at least something remotely close to the PHP-toolchain

Still, thx for the input :)

Yeah, I get you, in the past I've seen some tools that could detect dead code (which at the time wasn't interesting enough for me to bookmark it :s) but from what I can remember is that there should be some integration testing / CI tools that does that.

After looking around, I remembered that ESLint itself can detect dead code in the form of "no-unused-vars" errors that tells what variables/functions/methods/objects aren't being used (so dead or kinda, it may think that some of the above are dead whilst being used in other modules so a good JSDoc/Documentation is necessary).