Timothee Guerin

Not really, now sure how we can make this without it being very hacky and being a pain to maintain in the future. The problem here is the pipeline in...

So this is a problem that has come before and we decided to keep autorest more on the flexible side. The problem is how do we decide what is compatible...

By silent do you mean the SDK generate fine and compile fine(if applicable) but get published and is not usable? If so I don't think that would happen, the main...

This isn't something we have plan for right now. Will keep open for tracking

@lmazuel what was the reasoning for this one? Wouldn't just not having the parameter be the magic api-version param solve this? I trhink you you add this to the api...

Are you saying you want x-ms-client-name to apply to both the property name and the object name? If so the current behavior is expliclity deciding not to do that, I...

Oh I see, so the feature we were talking about on the other issue. Yeah that could be an option as well. This is not that breaking IMO specially if...

There is 366 specs using `api-version` with enum specified ```json { "specCount": 188, "providers": { "alertsmanagement": 10, "appplatform": 1, "attestation": 2, "blockchain": 1, "cognitiveservices": 4, "communication": 5, "confluent": 4, "cosmos-db":...

It does yeah unless, the parameter is marked with `x-ms-api-version: false` in which case it is treated as a regular param.

Directive are simple transforms running a given node, doing ref resolution is much more complex, this would also probably have unexpected consequence where you'd expect the parmeter to only be...