Bart Koelman

There's no need for a workaround anymore. Below are some scenarios, hope that helps. ```xml Exe net8.0 enable enable ``` So depending on your needs, choose one of the following:...

We had to change the OpenAPI document structure and introduce the extension at https://www.jsonapi.net/ext/openapi/ to support resource inheritance. Our OpenAPI package cannot function without that anymore. It is explained at...

Unfortunately, this is how our solution works. I wish things were simpler. The goal is to enable usage of all JsonApiDotNetCore features, which requires a JSON:API extension due to limitations...

So if I understand your use case right, that would be: only offer a documentation website and not care about client generators. This makes it annoying that there's a different...

I've tried the following combinations: - Only default media type - Only openapi media type - Default media type, followed by openapi media type - Openapi media type, followed by...

While re-reading the original question, step 4 might be the reason why it didn't work. If using the openapi extension, request/response bodies typically contain `openapi:discriminator` properties. These are _only_ allowed...

Yes, I know. I'm working on a fix, but I don't have much time at the moment to complete it. Thanks for the heads-up, though.

#1747 fixes the bug where the `Accept`/`Content-Type` behavior changes for existing endpoints after enabling OpenAPI. > So if I understand your use case right, that would be: only offer a...

Thanks for sharing. I'm curious what you'll come up with. Please use the master branch for exploration. It contains #1735, which eliminates subqueries when pagination is turned off in includes.

@bjornharrtell Are you still working on this?