Timothee Guerin

If PowerShell is the only generator and this is to support some legacy behavior why not use a directive to get the information you want. exposing that property now brings...

@dolauli yeah that looks like what I would be doing. Does this not work?

@dolauli can you confirm this is working https://github.com/Azure/autorest/pull/4692#issuecomment-1349059739? Another question is why is this just surfacing now?

Actually this is now causing some issue with flattening models. As `x-ms-enum` get included in the flattened type and this cause all kind of issues so most likely not going...

So given an enum what do you want? 1. enum with no x-ms-enum: 2. enum with x-ms-enum.modelAsString=true 3. enum with x-ms-enum.modelAsString=false What do you expect for each of one those...

So you want 3 different output? 1. primitive type 2. Some class 3. Enum

And the issue doesn't seem to be particularly related to `x-ms-enum` there seems to be something more broken about keeping extensions there. I don't really have time to investigate that...

Did we end up on the bundling the source as a solution or this is still on the table?

Autorest doesn’t support header, query parameters that are json(or other seeialization format) it only support the style options in openapi3

Hi @mdaneri, this feature is not on our roadmap at the moment, autorest supports only a subset of OpenAPI3 and this is the first time we got a request for...