WordPress / WordPress/WordPress-Coding-Standards
Add sniffs for deprecated WP features
Open
Nobody has claimed this yet.
Focus: WP interoperability
Type: Enhancement
- Dominant language
- PHP
- Stars
- 2.8k
- Forks
- 521
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 1
Description
Instead of finding out about a deprecated usage at runtime, we can use static analysis via PHPCS to list deprecated features. We should add sniffs for:
- Deprecated functions (calls to
_deprecated_function) - Deprecated constructors (calls to
_deprecated_constructor) - Deprecated files (calls to
_deprecated_file) - Deprecated hooks (calls to
_deprecated_hook)
See also https://github.com/gedex/wpdc
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
Review the repository's existing PHPCS sniff implementations and the linked wpdc project first. Define coverage for deprecated functions, constructors, files, and hooks identified through the corresponding deprecation calls; done means each requested category is detected by static analysis with appropriate coverage.
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
- Mostly clear
- Newbie friendliness
- 35/100