-
https://openactive.io/errors/unavailable_offer
Should error types be:
a) using the standard OpenActive namespace
b) using the standard schema.org / OpenActive namespace case and naming convention…
-
Another approach to test is having Django middleware check the requests and responses across the wire.
Two projects do that https://github.com/zlqm/openapi-toolset and https://github.com/Cohey0727/…
-
I would like to suggest adding Problem Details, [RFC 7807](https://www.rfc-editor.org/rfc/rfc7807.txt), to the document.
-
This text appears even when ASP.NET Core 2.1 is selected as the version:
> Client error response
>
> An error result is defined as a result with an HTTP status code of 400 or higher. For web API …
-
There are often models defined as a set of fields plus an `additionalProperties` of various types, such as `object`. For example, here is the schema for a `ProblemDetails` model which is a representat…
-
## overview
In terms of resource formatting with HAPIv2, we have a few options:
1. Continue our ad-hoc method of defining stuff as we go along
2. Adhere strictly to an external spec, like [JSON:API]…
mcous updated
4 years ago
-
### Is your feature request related to a problem? Please describe.
Starting with an ASP Core 3.0 API:
I return the result of `NotFound()` in my action.
```cs
[HttpGet("{id}")]
public async Task G…
-
### Problem
`ValidationProblemDetails` & `ProblemDetails` are classes introduced in ASP.NET Core 2.1 as a part of `Microsoft.AspNetCore.Mvc.Core` (https://www.fuget.org/packages/Microsoft.AspNetCore.…
-
I noticed that "links" key don't has underscore at beginning (_links), and this not conform to the vnd.error specs.
For example:
``` json
[
{
"logref": "error",
"message": "Could…
-
### Describe the bug
ValidationProblemDetails/ProblemDetails serialization to Xml uses incorrect casing
### To Reproduce
Steps to reproduce the behavior:
using ASP.NET Core 2.2
return a Validat…