WordPress / WordPress/Requests
DRAFT Roadmap Requests 3.0
Open
Nobody has claimed this yet.
Type: meta
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 500
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 5
Description
This issue is intended to contain a tentative roadmap for things to be included/removed in Requests 3.0.
For now, the most important function of this issue is to contain an action list to keep track of follow-up actions from current PRs/issues, which need to be handled in a future major release.
Action list
- Remove support for the deprecation notice silencing about use of the PSR-0 classes.
I.e. remove support for theREQUESTS_SILENCE_PSR0_DEPRECATIONSconstant.
Related: https://github.com/WordPress/Requests/pull/519 - Make more classes final. See #866
- Drop support for PHP < 7.2.
- Replace input validation in methods with parameter type declarations wherever possible.
Related: https://github.com/WordPress/Requests/issues/593 and #873 - Add return type declarations wherever possible (non-union types).
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 reviewing the action list and its linked PR and issues: PR #519, issue #866, issue #593, and issue #873. The roadmap is complete when each listed Requests 3.0 change has been separately scoped and implemented or otherwise resolved; no files or tests are named here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100