Juliette

@azaozz That sniff is very configurable, so you can make it work exactly the way you want already. See: * [Array alignment: allow for new lines](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/wiki/Customizable-sniff-properties#array-alignment-allow-for-new-lines) * [Array alignment: allow...

> I'm also thinking there should be couple of levels of warnings. One that would trigger a "fail" when testing certain code and another that would print output to the...

@azaozz Again, your examples would not be fixed that way by this sniff. Please read the property descriptions carefully, cause all this can already be configured.

@azaozz > Where can I set the maximum number of white spaces that will be inserted between key and => when aligning arrays? Sounds like you are looking for a...

WPCS can definitely not trace a variable back to its source as sniffs are mostly limited to one file only. In most cases, it can check that the first param...

@Potherca Thanks for opening this ticket. Here's my two cents regarding the "To be decided" tickets, which I largely base on semver reasoning: > Should these be completed before the...

One thing not mentioned in the above (but mentioned in comments in ticket #159) is "updating the namespace of the plugin to be in line with the new organisation the...

> Regarding changing the Packagist name, I would really like to do the rename but in a backward compatible manner. I have no idea how but I might be able...

> Are there other, non-code tasks we might still have to do? Prepare a human readable changelog which clearly lists any breaking changes ;-)

@Seldaek Thank you for confirming that renaming like that is still the only way to do it.