i'm right there with you guys. This PSR is full of inconsistencies, and insufficiently covers the full spread of language features. There are particular rules that *almost* form a pattern if you get really meticulous about what defines that rule, but it just seems so much simpler to say, "All curly braces should go on their own line. Period. End of rule." And so on...
Numerous complaints and concerns have been raised about this PSR in the last few months since the Review Phase was announced, and supposedly that's why it's still in Review. But there's been no additional public discussion by the members of the WG as far as i'm aware. For all intents and purposes, my team is going to use PSR-12 as a baseline, and lay our own rules on top of it to address the inconsistent patterns, missing pieces, and oddities that don't really make sense in our view. Since our product isn't open source, we don't really need to worry much about published contributions where this standard would be a factor. It's primarily a guideline to get all of our own internal design patterns aligned with each other. Unfortunate that this seems to be going stagnant (or worse, the feedback ends up ignored), because it was the most "rational" of the style guides i researched. -joe t. -- 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/3e748b90-f40b-4228-acef-ca5ce0174df6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
