On Monday, 23 April 2018 14:16:40 UTC+10, Daniel Hunsaker wrote: > > I often find it helpful to align operators other than assignment > operators, too. Comparison, bitwise, Boolean, arithmetic, and so on, are > equally subject to operand alignment to improve readability. Which is why I > said "operator" instead of "assignment operator", though my quick example > only included the one type.
Point taken, but I'm really more focused on the sort of code I posted originally. Leaving a rule completely open is fine, but I want to make sure that is the intention given it will absolutely lead to messy code (created by accident) not being detected by a static analysis tool. Once I release PSR-12 inside PHPCS, I now receive *all* bug reports when people don't agree with how it works, and I have to justify a standard I didn't write. It happened with PSR-2 (hence errata) and I found it much easier to deal with if I've already asked the questions and can point people to an answer by the authors. -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/658286a0-7fe9-4e0e-90bb-2919828343f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
