[corehttp] HttpResponseError lacks kwargs signature model compared with same class of azure-core

[msyyc]

HttpResponse lacks kwargs signature model compared with same class of azure-core

• corehttp:
  

• azure-core:
  

[github-actions]

@kashifkhan @xiangyan99

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[msyyc]

Not sure whether it is by design, but I think model signature is important. For example, when Typespec defines customized error like:

@error
model PetStoreError {
  code: int32;
  message: string;
}

(typepsec link)
The generated SDK will try to deserialize the response body with PetStoreError when error occurs then set it in model signature

            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = _failsafe_deserialize(_models.PetStoreError, response.json())
            raise HttpResponseError(response=response, model=error)

(generated SDK link)

so that SDK users could access the user-defined error model easily like:

try:
   client.op(...)
except HttpResponseError as err:
    print(err.model.code)
    print(err.model.message)

However, if corehttp doesn't have model signature for HttpResponseError, there is no other way to set the deserialized model for SDK users.