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
Don't really believe this is breaking, treating it more like a bug fix. This only impacts the class name of the operation group (which is technically public, but users shouldn't instantiate them), and the filename that this operation group is stored in (which is private). The operation group property on the service client stays the same
The text was updated successfully, but these errors were encountered:
iscai-msft
changed the title
remove double "operations" in oepration group names
remove double "operations" in operation group names
Mar 29, 2021
Decided not to make this fix after talking to @lmazuel . Reasons are:
users should never care about the operation group class name. They should only interact with the attributes on the service client, whose name is currently correct, so this change doesn't add any customer value.
This could cause errors when there didn't use to be any. Say, if a swagger defines operation groups Deployment and DeploymentOperations. Now, we create both operation groups with the same name, which will cause issues.
Thus, we're not making this change because there's not any customer improvement, and it opens us up to potential issues in the future
In the case of "DeploymentOperationsOperations", we should only have one Operations.
Don't really believe this is breaking, treating it more like a bug fix. This only impacts the class name of the operation group (which is technically public, but users shouldn't instantiate them), and the filename that this operation group is stored in (which is private). The operation group property on the service client stays the same
The text was updated successfully, but these errors were encountered: