We have a strict rule that requires name of a method in SDK [that wraps a POST apiCall] to match with action part of the Uri (the last segment of the Uri).
Let's say the Uri is:
POST /subscriptions/{subscriptionId}/providers/Microsoft.Subscriptions.Admin/moveSubscriptions
When conforming to above rule, the method name in SDK become moveSubscriptions (so operationId is YYY_MoveSubscriptions) At the same time linter produces a warning if the method name in operationId is not noun. These two validations are conflicting.
To discuss: Should we update our linter validations such as non-noun method name validation won’t be performed when the method name is derived from the POST action segment?
salameer
commented
6 years ago
We have a strict rule that requires name of a method in SDK [that wraps a POST apiCall] to match with action part of the Uri (the last segment of the Uri).
Let's say the Uri is:
POST /subscriptions/{subscriptionId}/providers/Microsoft.Subscriptions.Admin/moveSubscriptions
When conforming to above rule, the method name in SDK become
moveSubscriptions(so operationId is YYY_MoveSubscriptions) At the same time linter produces a warning if the method name in operationId is not noun. These two validations are conflicting.To discuss: Should we update our linter validations such as non-noun method name validation won’t be performed when the method name is derived from the POST action segment?