dakrone / dakrone/clj-http

Incorporate clj-http-fake

Open
#484 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
1.8k
Forks
410
PR merge metrics
No merged PRs in 30d

Description

Hi,

I'm trying to test that my custom middleware is applied. For that I had a look at clj-http-fake because it'd give me the chance to look at the produced request. However, it's 2 years old which I'd consider this unmaintained, it's might even be out of sync with clj-http.

I think it'd make sense for clj-http to ship with something like this, otherwise it's kinda hard to test a highly customized HTTP client.

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

Start by reviewing clj-http-fake and the clj-http repository's existing test setup; the issue names no files or tests. Determine the intended scope for shipping request-inspection support and how it should exercise custom middleware. Done should mean clj-http includes a maintained way to inspect produced requests while testing customized clients.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
backend, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.