Alain Schlesser

Namepaced functions seem to not be covered by the above. I have a project where the following notation is used, and properly supported by PHPStorm and PHPUnit: ``` @covers \Namespace\function()...

The use of `DIRECTORY_SEPARATOR` can actually break the code in some edge cases. For example, if you are running a CygWin environment under Windows, you're running a simulation of a...

Yes, this would work as expected: ```php class Employee {}; class Director extends Employee {}; class Janitor extends Employee {}; $injector->share( 'Director' ); $injector->share( 'Employee' ); $director = $injector->make( 'Director'...

I recently wrote a blog post about this: https://www.alainschlesser.com/interface-naming-conventions/ TL;DR: `Interface` suffix (or prefix) is an unnecessary form of [Hungarian Notation](https://en.wikipedia.org/wiki/Hungarian_notation), and actually severely limits your architecture (by making it...

@oscarssanchez This issue was fixed, however we couldn't fixed it in a general way without breaking backwards-compat. That's why you need to use the second argument to `display_items()` to make...

Fixed in #120

The GitHub icon is indeed meant to represent the repository as a whole, with the buttons next to it providing repository-specific actions. Also, to be honest, it is even hard...

@zzap Oh no, I think you misunderstood me. This should automatically generated based on the source code. Otherwise we'll have hundreds of links we'll need to check after each code...

We already try to simplify this by providing an overview in the issue templates: https://github.com/wp-cli/.github/blob/master/.github/ISSUE_TEMPLATE/1-BUG_REPORT.md#L20-L44 But yes, additional documentation in the handbook itself would be better.

I would love to have something like that available! I think that the use cases for scaffolding have by now outgrown the way this is technically handled, and it needs...