-
- [ ] Use custom error types to differentiate errors throughout the code base (as well as allow us to use different behaviours according to the type of the error). This can be an interesting resource:…
-
There is a RFC about default response type for API's in case of error.
> Abstract
This document defines a "problem detail" as a way to carry machine-
readable details of errors in a HTTP re…
-
Output of `curl -s cht.sh/~docker-compose` is too long, because the whole `:list` output is printed. Maybe show just a few lines of context for it?
```
[:list]
...
docker-build
docker-compose
do…
-
Output of `curl -s cht.sh/~docker-compose` is too long, because the whole `:list` output is printed. Maybe show just a few lines of context for it?
```
[:list]
...
docker-build
docker-compose
do…
-
Howdy!
I love the idea of this repository. We have tons of GCP Cloud Functions and Cloud Runs (what an awful noun). It can be hard for a dev to switch between the two, particularly to go to Cloud R…
-
Similar to https://github.com/solid/specification/issues/28
-
Respect the [RFC-7807](https://tools.ietf.org/html/rfc7807) norm to return HTTP responses.
-
### Describe the bug
`ProblemDetails` are serialized differently depending on how the XML output formatter is configured.
`AddControllers().AddXmlSerializerFormatters()` vs `AddControllers(o => …
-
There is a RFC 7807 for a response structure for error cases. For more details see https://tools.ietf.org/html/rfc7807.
For a form validation error it could be like this:
```
{
"type": "http…
-
I'm working on producing and consuming problem details as specified in [RFC-7807](https://tools.ietf.org/html/rfc7807) for better generation and handling of http entities for application error conditi…