@jrf_nl Do you know of any phpcs sniffs that implement the newer #PHPFig PER Coding Style 2.0?
In particular, I'm thinking about: “If a function or method contains no statements or comments (such as an empty no-op implementation or when using constructor property promotion), then the body SHOULD be abbreviated as {} and placed on the same line as the previous symbol, separated by a space.”
@danb@EdGrosvenor If we were able to set up some kind of governance structure like #PHPFig, then we could have community projects apply for “representation,” which would get them a voting seat, but we’d need to define a level of active participation their voter needs to maintain. They’d be the liaison for the project and would need to participate in discussions relevant to their project’s interests.
How does a screen reader read a hashtag that includes an acronym and a pronounceable word, like #PHPFig? I would say this as “P-H-P fig,” for example. How does a screen reader read it? I’d like to make my hashtags as accessible as possible.
The @phpfig PSRs should also define the names of the packages that include the interfaces, as well as the name used to indicate implementations of the PSR.
i.e., PSR-17 would include psr/http-factory and psr/http-factory-implementation, so I don’t have to go searching for these names every time.