WordPress / WordPress/WordPress-Coding-Standards
Restrict the use of private functions or classes that are not meant to be extended
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.8k
- Forks
- 521
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 1
Description
Once https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/pull/633 has been merged I will work on a list of private WordPress functions that should not be used by themes and plugins.
https://codex.wordpress.org/Category:Private_Functions
and WP_Internal_Pointers which is not meant to be extended.
The following are exceptions that would still need to pass.
remove_action( 'admin_enqueue_scripts', array( 'WP_Internal_Pointers', 'enqueue_scripts' ) );
remove_action( 'admin_print_footer_scripts', array( 'WP_Internal_Pointers', 'pointer_wp390_widgets' ) );
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 pull request #633 first, then use the linked Codex category as the source for the private WordPress functions list. Check how the repository's PHP_CodeSniffer rules represent prohibited usage and account for the two WP_Internal_Pointers remove_action exceptions. Done means the listed private functions and class are restricted while both exception calls still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100