Skip to content

Extend ReponseError to allow arbitrary types for error case #618

@ghostbuster91

Description

@ghostbuster91

This is a summary and continuation of two discussions:

As in openapi specification we are aware of possible error responses there should be an easy way to express that in sttp.

That would require adding another generic parameter to ResponseError , while default ResponseError would be still parametrized by String type.

Additional ResponseError type is needed in order to represent unmapped error codes.

All existing functions which deals with ResponseError (like asJsonAlwaysUnsafe) need to be refined.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions