eng, feeds, arm, update tspconfig template #2600
Conversation
|
No changes needing a change description found. |
|
You can try these changes here
|
weidongxu-microsoft
requested review from
bterlson,
markcowl,
allenjzhang and
timotheeguerin
as code owners
| @@ -19,7 +19,7 @@ options: | |||
| "@azure-tools/typespec-java": | |||
| package-dir: "azure-resourcemanager-{{#toLowerCase}}{{parameters.ServiceNamespace}}{{/toLowerCase}}" | |||
| namespace: "com.azure.resourcemanager.{{#toLowerCase}}{{parameters.ServiceNamespace}}{{/toLowerCase}}" | |||
| service-name: "{{#toLowerCase}}{{parameters.ServiceNamespace}}{{/toLowerCase}}" | |||
| service-name: "{{#toUpperCase}}{{parameters.ServiceNamespace}}{{/toUpperCase}}" | |||
There was a problem hiding this comment.
Is service-name supposed to be Pascal case or upper case?
There was a problem hiding this comment.
Pascal case.
Thanks. #toUpperCase would be wrong. How do I write "convert to Pascal case" here? I am still not sure what's the syntax used in this file.
There was a problem hiding this comment.
It's already with 'Pascal case'. You could close this PR.
There was a problem hiding this comment.
Unsure whether this is related.
ARM Resource Provider Name could be a same Microsoft.Workloads in all folders under https://github.com/Azure/azure-rest-api-specs/tree/main/specification/workloads, but each folder would generate different SDK and different service-name.
There was a problem hiding this comment.
This scaffolding template only supports a RP with single service scenario.
|
Per the above conversation, I think this should be closed. Please re-open or let me know if this is not the case. |
The
service-namein Java is recommended to be uppercase with whitespace.related to Azure/azure-rest-api-specs#34114