Jonas Lundberg

This looks very promising @kjagiello! Will do some testing and benchmarking.

Thanks for reporting .. there are tests with `ANY`, will try and add your specific case and see what breaks

I found the problem and it probably affected `headers`, `params` and `data` patterns as well, which uses the same `MultiItemsMixin` base class. @mikenerone, if possible, please try #289 before I...

Looks like a usable feature, will take a look, thanks

This is not `respx` related, and rather how `httpx.Response` is pickled/unpickled. Your solution looks reasonable, since content io, e.g. streams etc probably gives weird results when pickled.

@JacobHayes, new discussions regarding this has come up in #290 and we're leaning towards typing json as `Any` instead, to align with httpx. That should please `pyright` for you as...

You're right @viccie30, though we need to align with the `httpx` api here, rather than python's, since thats what we're mocking. Looks like [httpx is typing json as `Any`](https://github.com/encode/httpx/blob/26d48e0634e6ee9cdc0533996db289ce4b430177/httpx/_models.py#L831-L832), probably...

Looks like we've diverged from httpx on the request/encoding side as well .. also [typed as `Any`](https://github.com/encode/httpx/blob/26d48e0634e6ee9cdc0533996db289ce4b430177/httpx/_api.py#L47)

> I think you're right therefore to copy httpx's annotations. Yes, let's change to `Any` for the respond/response. About the request/encoding side, I think we're fine with current typing. We're...

> The current state of the art: [python/typing#182 (comment)](https://github.com/python/typing/issues/182#issuecomment-1320974824) Might be worth discussing, but since `json.loads` is typed to return `Any`, it may be incorrect to type it as your...