Replace guzzle with a PSR interface?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the Guzzle integration and the API client entry points in this repository. Determine which PSR HTTP client interface is intended and how replacing Guzzle would affect consumers, dependencies, and tests. Done means the client no longer forces Guzzle while existing API behavior remains covered.
Written by the indexing model from the issue text.
Description
It would allow projects using this library to pick their preferred HTTP client instead of forcing Guzzle.
- Dominant language
- PHP
- Stars
- 29
- Forks
- 9
- Avg merge
- 11h 38m
- Merged PRs (30d)
- 2
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.
More from GetStream/stream-chat-php
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
GetStream/stream-chat-php#140 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
GetStream/stream-chat-php#163 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
GetStream/stream-chat-php#114 · 2 comments ·
All issues in GetStream/stream-chat-php
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
coollabsio/coolify#11927 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100