You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v1 of PER is an exact replica of PSR-12, so adding support of the flag --per and using the psr12 as the underlying style guide might be a good point to start.
Expectation from PER is to go a gradual change in the guide as per the evolving nature of the language (more like "semvar", rather than following the PSR-1, PSR-2, PSR-12 changes - which take quite long to approve and adopt).
Even if no changes are done/approved as part of this issue, the idea is to highlight the ongoing changes so that efforts can start moving in this direction.
The text was updated successfully, but these errors were encountered:
PSR-12 standards would be replaced by PER (currently in progress).
Since we are currently supporting PSR-12, and I am assuming/hoping that PHP standards will always be supported (despite the focus on Laravel standards), so switching over to supporting PER would be something that we would have to do in near future, hence the recommendation.
Add support for PER : PHP Evolving Recommendation
https://github.com/php-fig/per-coding-style
https://github.com/php-fig/per-coding-style/blob/master/meta.md
Since v1 of PER is an exact replica of PSR-12, so adding support of the flag
--per
and using thepsr12
as the underlying style guide might be a good point to start.Expectation from PER is to go a gradual change in the guide as per the evolving nature of the language (more like "semvar", rather than following the PSR-1, PSR-2, PSR-12 changes - which take quite long to approve and adopt).
Even if no changes are done/approved as part of this issue, the idea is to highlight the ongoing changes so that efforts can start moving in this direction.
The text was updated successfully, but these errors were encountered: