-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] ArmResourceListByParent does not respect operation name but hard code to ListByResourceGroup. #37
Comments
There are actually template parameters that set this |
I think deferring to 'name' makes sense for parallelism, but we should then have a linting rule that promotes the |
You can do this with a projectedName decorator - this is necessary because we are using a decorator to enforce a particular naming pattern, here is a sample playground |
The decorator here is a legacy from when only interface templates were avaiable, and not operation templates. We should likely update the existing interface templates to use this decorator, update any existing specs to specify the correct name in their usage of the operation templates, and remove the decorator from the operation templates altogether. We may want to also add a linting rule to suggest correct naming patterns. |
…tly derived from op name (#1093) Closes #37 --------- Co-authored-by: Timothee Guerin <[email protected]>
Describe the bug
When using ArmResourceListByParent template, operation id is hard coded to _ListByResourceGroup
Expected behavior
listTest
should be correctly set in operation_id.The text was updated successfully, but these errors were encountered: