Tim Lovell-Smith

> > > I wonder if you can override that in some straightforward way. Any tips @leni-msft ? > > > > > > @TimLovellSmith I'm afraid no way to...

Refactoring to use common-types should help you fix some linter errors.

@paterasMSFT Hi Pateras, this PR has been stuck in draft status with no activity for a long time. I'm going to go ahead and close it. Please reopen it if...

> }, Common parameters best practice - use common types There are definitions of common parameters in commontypes types.json that you can use by $ref instead of declaring your own,...

> }, This looks like its based on the standard ARM SKUs contract? If so I wonder if we can get this included in common-types definitions --- Refers to: specification/storagecache/resource-manager/Microsoft.StorageCache/preview/2023-03-01-preview/storagecache.json:3101...

> }, I think I see you using this to declare resource ids - but resource ids aren't really fully qualified URLs - they are just absolute paths --- Refers...

> "/subscriptions/{subscriptionId}/providers/Microsoft.StorageCache/locations/{location}/ascOperations/{operationId}": { Are you using this to implement the Azure-AsyncOperation header pattern, here? https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#azure-asyncoperation-resource-format If so, the usual name for this resource type would be something like operationsStatuses. ---...

> "$ref": "#/definitions/CloudError" Error responses - use common types There are definitions of error responses and details in commontypes types.json that you can use instead of declaring your own. See...

> }, Best practice - Location parameters - use common types There are definitions of common parameters in commontypes types.json that you can use instead of declaring your own, like...

> } Best practice - OperationId parameters - Common parameters best practice - use common types There are definitions of common parameters in commontypes types.json that you can use by...