Automattic / Automattic/VIP-Coding-Standards
using curl should suggest using vip_safe_wp_remote_get instead of wp_remote_get
- Dominant language
- PHP
- Stars
- 261
- Forks
- 44
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
## What problem would the enhancement address for VIP?
When using `curl` the suggested fix is to use `wp_remote_get`, however, `wp_remote_get` is discouraged and `vip_safe_wp_remote_get` is suggested instead.
## Describe the solution you'd like
Suggest the use of `vip_safe_wp_remote_get` when using `curl` to avoid a secondary violation for using `wp_remote_get`
Contributor guide
Research direction
No file or test is named. Locate the PHP_CodeSniffer rule that reports curl usage and currently recommends wp_remote_get, then inspect its existing test coverage. Done means the diagnostic recommends vip_safe_wp_remote_get instead and no longer causes a secondary wp_remote_get violation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100