This PR deprecates the D3R-DEV-PHP.xml standard and makes it work the same as D3R-PHP.xml (which in #13 was aligned with D3R-PSR12.xml).
There is very limited use in CI environments and it is likely that only a small percentage of developers are using it locally. As the standard was intended to be a superset of D3R-PSR12.xml, no impact is expected.
After the release of https://github.com/D3R/github-workflows/pull/70, we can consider enhancing phpcs coding standards in a way that minimises disruption to developers. Specifically, we can introduce new rules as warnings, so annotations appear in PRs without preventing the PR from being merged. Therefore, there doesn't seem to be a clear need for maintaining a stronger standard for local use.
This PR deprecates the
D3R-DEV-PHP.xmlstandard and makes it work the same asD3R-PHP.xml(which in #13 was aligned withD3R-PSR12.xml).There is very limited use in CI environments and it is likely that only a small percentage of developers are using it locally. As the standard was intended to be a superset of
D3R-PSR12.xml, no impact is expected.After the release of https://github.com/D3R/github-workflows/pull/70, we can consider enhancing phpcs coding standards in a way that minimises disruption to developers. Specifically, we can introduce new rules as warnings, so annotations appear in PRs without preventing the PR from being merged. Therefore, there doesn't seem to be a clear need for maintaining a stronger standard for local use.