Skip to content

Conversation

@leewillis77
Copy link
Contributor

Adds a small explanation that running WordPress is not the same as running WordPress-Core,WordPress-Docs,WordPress-Extra as noted in #1440

@jrfnl
Copy link
Member

jrfnl commented Nov 26, 2025

Thanks @leewillis77, that looks like a valid addition.

I wonder whether people will raise the question "what is the difference" and whether it would make sense to answer that here.... Opinions ?

@leewillis77
Copy link
Contributor Author

I wonder whether people will raise the question "what is the difference" and whether it would make sense to answer that here.... Opinions ?

There's no documentation on what sniffs are included in which standard as-is so I don't think this is necessary, but I guess it may be useful, maybe just link the text to https://github.com/WordPress/WordPress-Coding-Standards/tree/develop/WordPress/Sniffs ?

@rodrigoprimo
Copy link
Collaborator

rodrigoprimo commented Nov 26, 2025

I'm not sure if that is what @jrfnl had in mind, but from my perspective, including in the note which sniffs are part of the WordPress standard and are not part of any of the subsets would be enough to answer the questions of what the difference is. What do you think?

@leewillis77
Copy link
Contributor Author

I'm not sure if that is what @jrfnl had in mind, but from my perspective, including in the note which sniffs are part of the WordPress standard and are not part of any of the subsets would be enough to answer the questions of what the difference is. What do you think?

My personal perspective is that it's too detailed for that document, but happy to add it into the PR if that's requested.

@leewillis77
Copy link
Contributor Author

If we were going to add the information I'd suggest a footnote something like this:

https://github.com/leewillis77/WordPress-Coding-Standards/tree/footnote-for-wp-standard-checks?tab=readme-ov-file#rulesets

Let me know if you would like me to update the PR to include this change.

@jrfnl
Copy link
Member

jrfnl commented Nov 27, 2025

Marking this PR as BLOCKED for the time being until the revived discussion in #1440 has been resolved.

Also see: #1440 (comment)

@jrfnl jrfnl added this to the Future Release milestone Nov 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants