-
-
Kind of a general issue, but the plugin should follow the established [WP Coding Standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/), which provides general guidance …
-
```
Make sure all code is PEP 8 compatible and passes all lint tests.
```
Original issue reported on code.google.com by `ricardok...@gmail.com` on 15 Jun 2009 at 11:14
-
The plugin code should follow WordPress coding standards.
-
I think the library should follow PSR2 coding standards. I've added tests to reflect the current coding standards based of PSR2 standards - and added automatic tests in TravisCI to see whether we adhe…
-
-
Something I've often seen teams neglect but is important for long-term maintenance and ease of collaboration is standardizing on coding and style standards, like https://google.github.io/styleguide/sh…
-
Write comments for all files in the project.
-
### Discussed in https://github.com/WordPress/developer-blog-content/discussions/160
Originally posted by **ryanwelcher** August 28, 2023
It would be great to go over the coding standard tools…
-
Now that we run `phpcs` against all core PRs, we should fix all existing coding issues in core to avoid getting so many warnings/errors. This issue (inspired by https://github.com/backdrop/backdrop-is…
ghost updated
10 months ago