This is a huge breaking change. Just imagine how many CI servers are going to explode due to sudden PSR2 violations when running phpcs.
If I had a vote here, I'd vote -1, because: 1) Most projects can't refactor their APIs entirely due to SemVer (and wouldn't even if they could, just to adhere to a styling standard). This will make every major project non-psr2-compliant, and will break its status as the de-facto standard. 2) If that rule must change, just get rid of it. Do NOT force projects to remove the suffix, just don't enforce the suffix anymore. That would be a minor change, as it's more permissive and therefore backwards compatible. 3) Let's be consistent and use the same rule to interfaces, abstract and traits (at least). - Pedro. -- 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/eaae419c-b94e-49f9-a976-be05be3ece49%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
