Add developer driven evolution document

[pshao25]

Addresses Azure/autorest.csharp#1945

[check-enforcer]

This pull request is protected by Check Enforcer.
For more information about how to run a pipeline against this pull request, see this.

[annelo-msft]

Would you please link the PR to the issue by putting "Fixes " in the issue description?

[annelo-msft]

I think we can restructure this to simplify it a bit. Instead of enumerating GET/PUT/POST/etc., what if we gave the rules for writing a convenience API?

• Replace the RequestContext parameter with CancellationToken
• Replace the input parameter RequestContent with a model type
• Replace the return value Response with Response<T>
• If you end up with an ambiguous call-site, rename the method
  • Add suffix Value or Values
  • If this isn't a good name, pick a good name for the method
• Create the models for the convenience APIs you've added

[pshao25]

I think we can restructure this to simplify it a bit. Instead of enumerating GET/PUT/POST/etc., what if we gave the rules for writing a convenience API?

• Replace the RequestContext parameter with CancellationToken

• Replace the input parameter RequestContent with a model type

• Replace the return value Response with Response

• If you end up with an ambiguous call-site, rename the method

  • Add suffix Value or Values
  • If this isn't a good name, pick a good name for the method

• Create the models for the convenience APIs you've added

Yes, I do follow this by giving rules, and I added more rules as you listed above. Enumerating GET/PUT/POST/etc. is just examples for how to improve to grow up method.

[annelo-msft]

Thanks!

We'll want to make sure we sort out the diagnostic scope questions and provide guidance for that before we GA -- @pshao25, would you create a separate issue for this, so we don't block this PR on that?

[pshao25]

diagnostic scope

[pshao25]

Thanks!

We'll want to make sure we sort out the diagnostic scope questions and provide guidance for that before we GA -- @pshao25, would you create a separate issue for this, so we don't block this PR on that?

Yes, created here: Azure/autorest.csharp#2115

[lirenhe]

LGTM

[pshao25]

/check-enforcer override