-
Make Error class more RFC 9457 friendly.
[The Problem Details JSON Object](https://www.rfc-editor.org/rfc/rfc9457.html#name-the-problem-details-json-ob)
[3.1](https://www.rfc-editor.org/rfc/rfc9…
-
We should discuss what our tests should look like for actual interop tests.
My current proposal is we create individual test credential fixtures, that are signed by each implementer, which will the…
-
**Is your feature request related to a problem? Please describe.**
I'd like to return errors in a "well known" format.
Namely the Problem Details format https://datatracker.ietf.org/doc/html/rfc9457…
-
In #67, we decided *not* to allow additional fields in serialization.
This means that any additional data we want to transmit needs to be _around_ a chunk, like:
```json
{
"chunk": {
"ser…
-
Looking at the 1.7.1 NGSI-LD specification:
> **5.5.3 Error response payload body**
>
> When reporting errors back to clients, NGSI-LD implementations shall generate a JSON object in accordance…
-
https://datatracker.ietf.org/doc/html/rfc7807#page-3
implement rfc7807 problem spec responses, opt into old format, deprecated
-
Right now, I see no way to directly set the `Type` of the error as the interface `StatusError` doesn't include a method, and `huma.NewError` also doesn't accept a `type` parameter! Maybe there is some…
-
Section 3.5 Processing Errors
https://w3c.github.io/vc-bitstring-status-list/#processing-errors
> - The `title` value SHOULD provide a short but specific human-readable string for the error.
> - …
-
Hello,
First of all, thank you for your project. 🤠
I've encountered an issue with the openapi-changes tool when trying to compare two OpenAPI specifications. Specifically, when I run the compariso…
-
**Problem description**
The current CAMARA error response has some drawbacks:
- It is proprietary (in the sense that nobody else uses it) requiring the API consumer to use proprietary error handler…