# `Mutare.Plug.Body`
[🔗](https://github.com/foxbenjaminfox/mutare_plug/blob/v0.2.1/lib/mutare/plug/body.ex#L1)

`:resp_body` — blanks the response body: the body argument of `Plug.Conn.send_resp/3`
and `Plug.Conn.resp/3` becomes `""`. A surviving mutant means no test reads the
response body — the response was sent, with the right status, and nothing checked
its contents.

    send_resp(conn, 200, Jason.encode!(payload))  # → send_resp(conn, 200, "")
    conn |> resp(:ok, body)                       # → conn |> resp(:ok, "")

Matches both calls written directly (`Plug.Conn.send_resp(conn, ...)`), aliased, or
bare-imported. A body that is already a literal `""` is left alone (the mutant would
change nothing). The status argument is handled by `:http_status` (atoms) and the
built-in literal families (integers); `send_file/3,4,5` is out of scope because its third
argument is a path, not a body — blanking it would cause a file error without testing
assertions about the response body.

Because the mutation is the original call with exactly the body argument substituted,
`Mutare.Transform.Overlap` treats it as covering that node: on a *literal* body the
built-in `:string` leaves (`""`/`"mutare"`) are pruned automatically, so this family
supersedes them rather than double-firing on the same range.

---

*Consult [api-reference.md](api-reference.md) for complete listing*