meilisearch / meilisearch/meilisearch-ruby
Switch to Faraday?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 224
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Description
Consider using Faraday instead of HTTParty?
Basic example
Currently, the Meilisearch gem is using HTTParty, which is a great HTTP client library that's been around for a long time. It is, however, very rarely updated, and most libraries in the wild are now using Faraday as their HTTP client. I was wondering if you'd consider making a switch to Faraday?
I'd also be happy to put together a PR to do so, but didn't want to be presumptuous and waste your time and mine if you all feel strongly that HTTParty is the way to go. Please let me know!
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
No files, tests, or entry points are named. Start by locating the Meilisearch gem's HTTParty usage and reviewing how its HTTP client behavior is covered by tests; the work would be complete when the client uses Faraday with equivalent behavior and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100