How to use special/unofficial HTTP status code?

[longquanzheng]

Hey I am using a 420 status code for my swagger:
https://github.com/indeedeng/iwf-idl/blob/d104cfc4cd756787d685d1ccf41bc43ebe9d85ab/iwf.yaml#L225
It has been working fine with other languages (Java/Golang)
But I got error when generating python code:

WARNING parsing POST /api/v1/workflow/rpc within default.

Invalid response status code 420 (not a valid HTTP status code), response will be ommitted from generated client

Is there a way to workaround this error here?

Thanks!!

[dbanty]

Not possible today. I’d be open to a PR which allows for non-standard codes, but there are a few things to sort out:

1. How to enable this without removing type safety for APIs which use standard codes, meaning most clients should still use the current class and not have int added to their type signatures.
2. Test to make sure that httpx allows for this, I believe it should but we need to confirm.
3. Make the non-standard codes type-safe. I could either see replacing HTTPStatus with int, or switching to a union for APIs which use non-standard codes.

[Ykrej]

I have opened #1407 implementing support for non-standard status codes.

1. Genericizing Response.status_code to int or http.HTTPStatusCode and filling in this new generic param during codegen
2. Httpx doesn't mind receiving responses with non-standard status codes
3. Number one solves this problem and avoids having to do isinstance() checks every where