WordPress / WordPress/Requests

Please provide CLEAR announcement about moving Requests to WordPress

Open
#930 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
3.6k
Forks
500
Avg merge
2d 21h
Merged PRs (30d)
5

Description

I have used this library in my project, today for some reason (probably for the sack of documentation) I came to github and found WordPress (instead of some weird prefix rmmc... something (pun intended). And I was surprised, if I am at the right library or not...

Then I googled, I found https://requests.ryanmccue.info/
Here no where mentioned WordPress (apart from git clone :p)

Later I asked Chatgpt (even Google aka Gemini, "Is php request the same as Wordpress Request" and it replied..clear No, both are different and blah blah..

Then I used chatgpt's deep research. Chatgpt found the changelog, etc..blah blah, to confirm it is indeed transferred..

In a nutshell, why is it so hard to even figure out if this library is transferred to WordPresss? I do understand that for backward compatibility the namespace in composer is maintained, but on the top of the composer and also on the library website, you should mention the announcement about the transfer, so a dev coming from an ancient past could understand and adopt, instead of wasting half an hour or so. I am making this issue out of frustration and also out of my empathy (to save other devs to waste their time),
so actionables could be:

  1. On github readme please mention a note
  2. On composer mentioned the note
  3. on the lib website mention the note,
    Or whatever else a better u can find.

C ya,
Tabu :)

References:
https://chatgpt.com/share/67d2d491-6c8c-8003-9f7c-4668215bd63f
https://requests.ryanmccue.info/
https://packagist.org/packages/rmccue/requests

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the GitHub README, the Packagist page for rmccue/requests, and the requests.ryanmccue.info website referenced in the issue. Add a clear explanation of the move to WordPress and the retained package or namespace naming where appropriate; done means users can identify the project's relationship from each listed entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.