Timothee Guerin

Yeah looking at it, not including the type would mean that this is `any` type. I am guessing this was done for a few reason: - Helping teams migrate with...

However because this is used with `additionalProperties` which means that it is a `Dictionnary` as far as I understand and should have` type:"object"`https://swagger.io/docs/specification/data-models/dictionaries/?sbsearch=additionalProperties

Actually we do support any, there is an `AnySchema` in m4, it can just be done without providing anything on it. ```json { "swagger": "2.0", "info": { "title": "Recursive", "version":...

I agree that this is terrible and it can be quite trivial to do that check but this is the job of the azure-rest-api-specs linting. Autorest shouldn't fail on that....

This unfortunatelly seems to be an issue with the underlying library for resolving files https://github.com/TooTallNate/file-uri-to-path/issues/8

Yeah this is because this warning is emitted much later in the process where the files have been merged together so it can't map back to the original location.

Well there could be something but it isn't a simple fix. Autorest has a source map system to trace back where something is from. It has however caused many performance...

See how Cadl will take this into account. https://github.com/Azure/cadl-azure/issues/1028

Check if it fails correctly and close as by design. Workaround can be used if really on purpose.

Yeah, I think this is due to how references are expanded at the beginning but not again later. you can use `$documentPath` to make the full reference "$ref": "$documentPath/../network.json#/definitions/Resource" We...