or "FIG-R"
The idea behind the group is to address errors made in the actual FIG PSRs and to rectify those
before it's too late.
If other folks want to adopt what we are doing they are welcome to do so, but that is not the aim.
If other folks feel forced to adopt what we're doing they are welcome to
do so, and they most certainly will. Right?
Because it seems to be necessary. Coding standards should not evolve out of political decisions, but reasonable arguments.
First of all FIG itself did make mistakes in their drafts resulting in a wrong standard now. They knew it and always talked it down as "internal group decisions" not affecting the rest of the PHP world. But they very well knew it would at some point, as more and more adopt to it due to a lack of guidance making it the "de-facto standard" these days.
People are not taking a library, framework or code seriously these days, just because it is not complying to FIG PSR(-2), by using tabs for example (as it might always have and as it should have).
This addresses this issue in the PHP community.
- PSR-2-R - "PSR-2 with tabs and consistent brace style"
- PSR-2-R Additions - optional coding standard recommendations
- Reasoning behind it and a Spaces-vs-Tabs and Brace-Styles evaluation
You can copy this snippet:
[](https://github.com/php-fig-rectified/fig-rectified-standards)
| Num | Title | Code |
|---|---|---|
| 0 | Autoloading Standard | PSR-0 |
| 1 | Basic Coding Standard | PSR-1 |
| 2 | Coding Style Guide | PSR-2-R |
| 3 | Logger Interface | PSR-3 |
| 4 | Autoloading Standard | PSR-4 |
Check out the psr2r-sniffer repo, which contains a sniffer that can not only report all CS issues but also auto-fix most of them.
- Undeceive more lost souls. If everyone used PSR-2-R, FIG would have to revise their standard.
- Help to make the FIG people understand what errors they made (and as a result damage they caused by deliberately forming an inconsistent standard) and how they can rectify them.
See the original FIG repo.