WordPress / WordPress/Requests
Parse cURL error messages for better exceptions
Open
Nobody has claimed this yet.
Component: Transports
Type: enhancement
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 500
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 5
Description
Our exceptions for cURL at the moment fall into a single bucket. Rather than having transport-specific exceptions, these should use a common set of names.
(In addition, we can probably improve the names and namespacing.)
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 cURL exception handling and the existing exception definitions. Compare the current transport-specific exceptions with the proposed common set of names and namespacing, then establish the intended exception mapping and update coverage before changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100