Stéphane Erbrech

I asked the same question recently to @jhendrixMSFT Let me provide a use case to put the feature request in context. We want to follow an api first design process....

somewhat related: https://github.com/Azure/autorest/issues/4456 this would also help us in an API first process, because the API that the swagger defines is not necessarily implemented by a single service, so it...

Do you have a list of the changes required to be done? It will be easier to jump in and help if there was a documented plan. :)

The doc is wrong as well. MutuallyExclusiveSet option works in exactly the opposite way as documented in the wiki : ``` csharp class TestOptions { [Option(MutuallyExclusiveSet = "web")] public string...

Hi, Well, It's been a while now, but thanks to get back to me. Why do we need to set a flag to enable the feature? Why isn't it on...

My thinking : The feature does not intersect any other feature : Turning it ON does not change the behaviour of existing code that is not using this feature explicitely....

It's much clearer now 👍

Maybe every response should provide a way to inspect the underlying response, like the `policy.Request`, which exposes `.Raw()` Could all response type be extended to expose a .Raw() func that...

Oh, wow... yes, I think this "solves" it, but it's really weird and not discoverable at all. looking at the doc, I just noticed this : [`WithHTTPHeader` ](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/[email protected]/runtime#WithHTTPHeader). I wrote...

"users don't care about the raw HTTP response". obviously we do. when we get an error, the AzureError has an operationID and correlationID, and we want to track that in...