sync core library, prepare typespec-java 0.41.0 and autorest.java 4.1.63#3298
sync core library, prepare typespec-java 0.41.0 and autorest.java 4.1.63#3298XiaofeiCao merged 15 commits intomainfrom
Conversation
This reverts commit da7a11b.
|
when I am running on local it seems OK 
|
|
maybe similar to this microsoft/typespec#6662 and to this day we has code in tsp-client like this though 3.7.2 is fine too, we are not likely to bump version anyway. |
Yeah, exit code is 0 for 3.8.0. Pipeline failure likely be caused by stderr. We could merge stderr into stdout as you mentioned. Curious why Anyway, I'll stick to pinning autorest version. |
- emitter part for Azure/azure-sdk-for-java#47621 - autorest PR: Azure/autorest.java#3298 - sdk repo PR: Azure/azure-sdk-for-java#48226 - sync SDK PR looks good: Azure/azure-sdk-for-java#48179 ## Summary Replace `AzureResourceManager` with SDK-specific `XXManager` as the entry point in Fluent Premium samples. Previously, premium samples were generated with `AzureResourceManager` as the entry type and then moved to `sdk/resourcemanager/azure-resourcemanager/samples` by the downstream `generate.py` script. This change makes premium samples use the corresponding `XXManager` (e.g., `ComputeManager`, `StorageManager`) directly, so samples can stay in their own SDK location. ### Before vs After ```java // Before: premium sample used AzureResourceManager void sampleMethod(com.azure.resourcemanager.AzureResourceManager azure) { azure.storageAccounts().manager().serviceClient().getStorageAccounts().list(); } // After: premium sample uses SDK-specific manager void sampleMethod(com.azure.resourcemanager.storage.StorageManager manager) { manager.serviceClient().getStorageAccounts().list(); } ``` Will update `generate.py` when this got shipped.
|
if you plan release, take microsoft/typespec#9926 with it |
XiaofeiCao
changed the title
2 participants
No description provided.