P. Raj Kumar

@bjornsnoen - Gotchu. As you mentioned, I think it makes sense to assume that the package supports type checking, considering the usage of type annotations throughout the docs. IIUC, to...

@mikeholler, have you tried using a [`@response_handler`](https://uplink.readthedocs.io/en/stable/user/quickstart.html#response-and-error-handling)? > @response_handler registers a callback to intercept responses before they are returned (or deserialized)

Hey, @returnnullptr - thanks for reporting! I think you caught something deeper. #258 should fix this.

Hey, @HarvsG - Got it. The fix will be part of v0.9.7, which I'll be releasing this week. ETA is by March 11th

v0.9.7 is live now and includes the fix for this issue

@HarvsG - Interesting.. I might have missed something, or you might be running into a similar issue with a different cause. Could you check out [this test case](https://github.com/prkumar/uplink/blob/master/tests/integration/test_handlers_aiohttp.py#L32) and let...

@joeld1 - The file upload behavior you are encountering may be caused by an issue identified in #183. Can you try adding the workaround mentioned in https://github.com/prkumar/uplink/issues/183#issuecomment-562621257 to your script?

Here is a code snippet that summarizes some thoughts I had regarding the requirements for this feature: ```python from uplink import Resource, Consumer, get, timeout, retry # On its own,...

Another helpful concept could be the `Entity`, which removes the reliance on the consumer for making calls against a specific instance of a resource: ```python class Order(Entity): def __init__(self, response):...

I'm looking into different approaches for how we can address this. The approach I'm favoring presently is to define a new decorator (e.g., `converters.pydantic.dict_args(...)`): ```python @json @returns.json @converters.pydantic.dict(by_alias=True) @post("scenario") def...