Coding Standards: Use WordPress packages for coding standards - Step 1 #62
Conversation
First pass at improving the formating and linting. Before a big fix, I wanted to get this agreed on and likely also get a few other PRs merged.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core SVNCore Committers: Use this line as a base for the props when committing in SVN: GitHub Merge commitsIf you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
I'm planning to do this is three main chunks:
|
desrosj
changed the title
|
Your plan sounds great to me. I think after #64 is merged we can proceed with steps 2 and 3. The other PRs remaining are experimental attempts at fixing an issue. |
Continues what was started in #62. Only substance change is converting from `.map` to `.forEach` when there is no return.
Continues what was started in #62. This is step 2: Reformat everything and step 3: add an action. Lots of pinking shears were used here. Only substance change is converting from `.map` to `.forEach` when there is no return. Co-authored-by: aaronjorbin <jorbin@git.wordpress.org> Co-authored-by: desrosj <desrosj@git.wordpress.org>
First pass at improving the formating and linting. Before a big fix, I wanted to get this agreed on and likely also get a few other PRs merged.
What?
The coding standards should be the same as elsewhere in the WordPress project.
Why?
Consistent styles make it easier for people to contribute.
Testing Instructions
Does it work?