WordPress / WordPress/WordPress-Coding-Standards
Remove support for PHP 4 coding practices from sniffs
Open
Nobody has claimed this yet.
Type: Chores/Cleanup
- Dominant language
- PHP
- Stars
- 2.8k
- Forks
- 521
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 1
Description
Placeholder issue for action in WPCS 4.0.0.
-
WordPress.NamingConventions.ValidFunctionNamesniff: remove exceptions for PHP 4 constructor/destructor methods.
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 WordPress.NamingConventions.ValidFunctionName sniff and reviewing how it handles PHP 4 constructor and destructor method exceptions. Done means those exceptions are removed for the WPCS 4.0.0 action and the sniff’s existing checks continue to pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100