Bart Koelman

> The Microsoft.AspNetCore.OpenApi implementation has evolved to cover some of the scenarios that you listed originally including... These are great, thanks. The last one I don't understand, can you clarify?...

Regarding `allOf` vs `anyOf` usage for inheritance: I discovered that Swashbuckle changed its default from `allOf` to `anyOf` not too long ago. However neither NSwag nor kiota function properly with...

> At the moment, I'm not super eager to expose too much of M.A.OpenAPI's schema generation pipeline, particularly as we look towards a future where JSON schema is more unified...

@RicoSuter Would you mind indicating your preferred solution here? I want to get some input to determine future directions for my project. And can you please tag the core contributors,...

@lahma I'm not getting any response on this, can you please take a look?

@lahma Thanks for responding. Any tips on getting his attention? The minimal solution would be to split the template into separate files, which is a non-breaking change. I'd be happy...

Closing, we don't need this anymore. Turns out we can abuse the "Prism" class style to intercept `INotifyPropertyChanged` by overriding the (relatively small) `Class.Inheritance.liquid` template, which sets to our own...

Great tips at https://engincanveske.substack.com/p/my-notes-from-googles-technical-writing.

Should review all places in the JSON:API spec where meta can occur, and possibly update JADNC accordingly. Then review the OpenAPI models, including atomic operations.

Hi @mus65, thanks for reporting this. Some background on what's happening here: When a project has multiple OpenAPI references without any settings, each client generates its own `ApiException` class. That's...