explore compiler defaulting host parameters from literals to strings with the literal value as a default

[iscai-msft]

Clear and concise description of the problem

There's continued discussion over whether host parameters should be generated as literal values, when guidelines say that host is something that can always be overridden. We don't want to make users explicitly define host as a value with a default every time, but emitters would like the . TCGC is going to special-case host params to be strings with default values (issue here), this issue is to eventually explore having the compiler do this instead of tcgc, which would be preferable if this is something that we want to provide to all emitters and emitter authors.

Checklist

• [X] Follow our Code of Conduct
• [X] Read the docs.
• [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[timotheeguerin]

Needs more info on what do you actually expect. And in scenarios like that what would you even want Playground

• When a server already parameterized
• When multiple server
• When multiple server including one parameterized and some not
• When multiple server all parameterized differently

[weidongxu-microsoft]

I assume the "guidelines" here is Azure guideline, i.e. flavor=azure.

Would TCGC behave differently, if e.g flavor=generic ?

[timotheeguerin]

I think if anything people 3rd party are way more likely to want to always have the baseUrl overridable.

[microsoft-github-policy-service[bot]]

Hi @iscai-msft. Since there hasn't been recent engagement, we're going to close this out. Please feel free to reopen if you have any further questions or concerns.