Implementing PSR-18 adapter for amphp/http-client v5
Open
Nobody has claimed this yet.
feature request
- Dominant language
- PHP
- Stars
- 731
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
Thanks to fibers, the amphp/http-client v5 has a "sync" interface: it gets rid of promises & generators. It is now possible to implement the PSR-18: HTTP Client.
Benefits:
- Any sdk that requires a
psr/http-client-implementationcould become asynchronous when used with AMP. - Any PSR-18 middleware could be used
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
The issue names the amphp/http-client v5 sync interface and the PSR-18 HTTP Client specification, but no repository files or tests. Start by reviewing those interfaces and the existing client entry points; done means providing a PSR-18-compatible adapter that enables PSR-18 SDKs and middleware to work with AMP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100