You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now you will see the route becomes /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContosoProviderHub/locations/{location}/employees
Please correct me if I'm wrong:
I assume the resource type for this route is Microsoft.ContosoProviderHub/locations/employees, which is different from the other operations, whose resource type is Microsoft.ContosoProviderHub/employees
I assume getArmResources will return all of the operations including listByResourceGroup for resource model Employee right? Something like
pshao25
changed the title
Customize path parameter for a resource operation
Customize path parameter for a resource operation changes its resource type
Jan 7, 2025
Use this Employee example, the only change I made is adding a path parameter to listByResourceGroup like
Now you will see the route becomes /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContosoProviderHub/locations/{location}/employees
Please correct me if I'm wrong:
I assume the resource type for this route is Microsoft.ContosoProviderHub/locations/employees, which is different from the other operations, whose resource type is Microsoft.ContosoProviderHub/employees
I assume getArmResources will return all of the operations including listByResourceGroup for resource model Employee right? Something like
If that is the case, we implicitly add a new resource with another resource type, I feel like that not what TypeSpec should do.
Currently, .net SDK's behavior (swagger input) is listByResourceGroup operation doesn't belongs to Employee resource model.
The real case is from this operation.
The text was updated successfully, but these errors were encountered: