-
See https://github.com/juhaku/utoipa/issues/590. It would be useful to allow `utoipa` to support RFC-7807 through this library.
-
l00mi updated
1 month ago
-
## I suggest
Use problem+json rfc 7807, together with SOAP 1.2 faults to avoid inconsistencies in schema
and implement a global error-management strategy.
https://github.com/ongov/API-Guideline…
-
## Description
This is a tentative roadmap, I will update it as things evolve. Some things might be discarded, others might be added later. I didn't want to make it fully public as it could raise e…
-
Work has begun updating RFC 7807 with [rfc7807bis](https://github.com/ietf-wg-httpapi/rfc7807bis). With the opportunity this gives, I've suggested in ietf-wg-httpapi/rfc7807bis#10 to create an officia…
-
**Is your feature request related to RFC7807? Please describe.**
The positive experience of RFC 7807, whose journey began in 2016, is concluded (**deprecation**) but also confirmed with a new offic…
-
I am wondering about the correct Content-Type header to use when returning an exception.
From [here](https://github.com/opengeospatial/ogcapi-common/blob/master/core/clause_11_media_types.adoc#prob…
-
External Documentation is not rendered if it's inside root of the schema. However there are no problems if external docs are located inside any property of an object.
Schema minimal example:
```…
-
### Problems and suggestions:問題・課題点/提案
In the case of an error, since the JSON format is not fixed, it is difficult to use for the client.
ex.
1. Response at mandatory error when posting to `/commu…
-
The default error handling of FastAPI is a bit weird. You get response bodies such as
```
{"detail":
[
{"loc": ["body", "title"], "msg": "field required", "type": "value_error.missing…