Darrel
This is a new escape character in Yaml 1.2. I will create a PR in SharpYaml to add support for it.
The current version of the OpenAPI specification says this scenario is invalid. http://spec.openapis.org/oas/v3.0.3#path-templating-matching ``` The following paths are considered identical and invalid: /pets/{petId} /pets/{name} ``` This has been the case...
Yes https://opentelemetry.io/ is what we should be looking at. We should also follow the Azure SDK logging policies https://azure.github.io/azure-sdk/general_azurecore.html#logging-policy unless we have good reason not to. Ideally we want people...
> I don't think the logging should be added to what we generate, but only in the "handcrafted" code. Agreed. Abstractions - I don't think so. Http - definitely Auth...
OpenApiStreamReader.ReadAsync() throws an InvalidOperation exception when using ResolveAllReferences
As mentioned in the [release notes](https://github.com/microsoft/OpenAPI.NET/releases/tag/1.3.0-preview) currently remote references only works for absolute paths.
OpenApiStreamReader.ReadAsync() throws an InvalidOperation exception when using ResolveAllReferences
I'm working on fixing this at the moment. Thanks for the repro instructions.
Check out the ResolveReferences code. When we read references we create an empty object with just the Reference property set. After the read is done, we run the ResolveReferences to...
Tag is a bit of a funny bird because it is effectively referenceable, but doesn't use $ref to do the referencing. It's similar to SecurityScheme. I'll need to dig into...
As this problem only occurs when consumes is declared after paths/components I am going to defer fixing this. The fix needs to go into v2\OpenApiDocumentDeserializer.
It was a design error to try and interpret the data types of example values. We should never have tried to do it because it causes way too many problems....