James Hinshelwood

> Hey @JamesHinshelwood, thanks for the contribution! I am wondering if maybe we should just expose the underlying `httpx.Response` object within our own `Response` class that comes back from the...

I've updated this PR with what I (hopefully) described above. Let me know what you think.

> Raising on 2xx responses doesn't feel right to me, why do you feel it's needed? A lot of APIs use 201 and 204, for example. If the `openapi.yaml` specification...

**EDIT**: The issue I've encountered below was actually https://github.com/dermesser/yup-oauth2/issues/161 I'm running into a suspiciously similar problem but with the ServiceAccount flow. My token looks like: ``` {"timestamp":"Aug 12 19:08:11.303","level":"DEBUG","fields":{"message":"received response;...

To answer what would be desired from my side... All I would want is to serialise and deserialise 3.1.x OpenAPI documents. The only other bit of tooling we're using is...

I had a go at adding support for 3.1.x in a branch here - https://github.com/JamesHinshelwood/openapiv3/tree/openapiv3.1 The basic approach is that we have entirely distinct `OpenAPI` structs for 3.0 and 3.1,...

Thanks for the positive comments. I will try and find some time in the next week to clean up my branch and submit it as a PR here so we...

I would like to give this a go @rustbot claim

Hi, apologies. Life has got in the way and I don't think I'll be able to work on this soon. Will unclaim in case someone else wants to. @rustbot release-assignment

@gwenshap Thanks for the offer. It will be a while before I can look at this again. If you're willing to rebase and address @dbanty 's comments I'd be very...