Prepare for WPVIP: Never use `$_REQUEST`
Open
Nobody has claimed this yet.
featurerequest
VIP-compliance
- Dominant language
- JavaScript
- Stars
- 2k
- Forks
- 975
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 36
Description
We are currently using $_REQUEST on three different locations.
The code standards of VIP dictate that it should never be used.
It can be easily converted to a conditional $_POST/$_GET/filter_input structure.
See https://vip.wordpress.com/documentation/code-review-what-we-look-for/#using-_request
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
Search the repository for the three uses of $_REQUEST and inspect their surrounding input handling. Read the linked WordPress VIP coding guidance, replace each use with the appropriate $_POST, $_GET, or filter_input approach, and verify that no $_REQUEST usages remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100