Darrel

You will struggle to process the complete public metadata on Graph because there are a number of containment annotations that are lies for legacy reasons. Unfortunately the lies cause the...

@PerthCharern The guard clause isn't necessarily bad, it's just a whole lot of boilerplate code to maintain. Everywhere where we currently have just get;set property declarations would need to be...

I made progress on this. Hopefully will be able to share something soon.

@selman92 Have you tried with the latest version of the library? I tried your example in the workbench tool and got the following: ``` openapi: 3.0.1 info: title: Foo version:...

additionalProperties is true by default. Is there a reason why you want additionalProperties to be emitted in the output? The challenge we have is knowing when to emit default values....

@unparalleled-js Just for clarity, that's not the spec. The OpenAPI specification is here https://spec.openapis.org/oas/v3.1.0 I will reach out to the Smartbear team who write the docs you referenced to add...

@mlafleur The two schemas you are showing are functionally equivalent. The default value of additionalProperties was not defined well in OpenAPI 2.0 and so some tooling (i.e. AutoREST) assumed the...

@Shwetap05 What's the priority on this bug? I'd like to get a 1.0.1 patch release out because I need the other fixes I don't in a release package. Do you...

@Shwetap05 Cool. I'll take a quick look and see if it's an easy fix. If it is I'll try and get it into 1.0.1

@Shwetap05 So.... there is probably no easy answer to this. The original V2 document is arguably invalid. By declaring both `application/json` and `application/x-www-form-urlencoded` for the `consumes` property it becomes challenging...