-
Notifications
You must be signed in to change notification settings - Fork 55
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
'in' operator is less robust than other options for deriving key presence #440
Comments
@Packmanager9 The current code assumes that ms-rest-js/lib/serviceClient.ts Lines 721 to 731 in 386ed0f
The only call to this method is on a ms-rest-js/lib/serviceClient.ts Lines 663 to 664 in 386ed0f
|
Sure, here's the snippet I was using. msRestNodeAuth.interactiveLogin().then((creds) => { |
@Packmanager9 could you please try wrapping the arguments to -client.workflows.listBySubscription(top, filter)
+client.workflows.listBySubscription({top, filter}) The method expects an options object listBySubscription(options?: Models.WorkflowsListBySubscriptionOptionalParams): Promise<Models.WorkflowsListBySubscriptionResponse>; |
@Packmanager9 it's been a while, have you got a chance to look at the above suggestion? |
Problem:
Given that the 'in' operator will throw an error error and fail: 'Cannot use 'in' operator to search for 'top' in 1'
(Line 4959 in 'msRest.node.js)
Solution
A different method of deriving the key presence could be used.
Original:
Proposed:
Alternatives:
Tried removing the check all together, immediately fails.
The text was updated successfully, but these errors were encountered: