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
I was wondering if there could be a way for developers to start working and creating sniffs on these PSRs (PSR-5 - PSR-12)
For instance I have a sniff that checks for deprecated PHPDoc tags according to PSR-5. If I make a PR creating a new standard named PSR-5 having only this sniff will it be accepted? This way more developers can influenced to create more PRs about these PSRs.
I know that these PSRs are currently in Draft state and you might reasonably say that things might change but for instance for the sniff that I mention I don't think that these tags that are deprecated in PSR-5 will become un-deprecated.
The text was updated successfully, but these errors were encountered:
Yes, I would accept that PR. But given they are in draft, I'd rather include them in the 3.0 branch because I don't think the PSRs will be approved before 2.x has finished its run. I don't want to include an incomplete (or worse, incorrect) standard in there.
I was wondering if there could be a way for developers to start working and creating sniffs on these PSRs (PSR-5 - PSR-12)
For instance I have a sniff that checks for deprecated PHPDoc tags according to PSR-5. If I make a PR creating a new standard named PSR-5 having only this sniff will it be accepted? This way more developers can influenced to create more PRs about these PSRs.
I know that these PSRs are currently in Draft state and you might reasonably say that things might change but for instance for the sniff that I mention I don't think that these tags that are deprecated in PSR-5 will become un-deprecated.
The text was updated successfully, but these errors were encountered: