Code style should enforce documentation for actions and filters
Open
Nobody has claimed this yet.
Status: wait for upstream/WordPressCS
Type: enhancement
- Dominant language
- PHP
- Stars
- 22
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
every do_action and apply_filters should be documented.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing code-style checks for WordPress actions and filters, then review how they detect and report violations. Clarify what counts as documentation for each hook and how the repository tests coding-standard rules. Done means both do_action and apply_filters usage are consistently checked with coverage for the expected documented and undocumented cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100