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
Right now recordings generate code that, among other things, include a builder pattern with a function that is named after the HTTP verb. The problem is that the scope may not support that verb.
A better solution would be to generate (at least for the ones that are not trivial / supported) the recordings with a generic http verb processing mechanism.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you!
lockbot
locked as resolved and limited conversation to collaborators
Sep 14, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now recordings generate code that, among other things, include a builder pattern with a function that is named after the HTTP verb. The problem is that the scope may not support that verb.
E.g.:
nock('http://ciserversdk.table.core.windows.net:80')
.filteringRequestBody(function (path) { return '';})
.merge('/tableservice12(PartitionKey=%27part1%27,RowKey=%27row1%27)', '')
.reply(204, "", { 'cache-control': 'no-cache',
'content-length': '0',
date: 'Thu, 21 Feb 2013 00:30:56 GMT' });
A better solution would be to generate (at least for the ones that are not trivial / supported) the recordings with a generic http verb processing mechanism.
Example:
.request('merge', 'tableservice12' foobar)
.reply(foobar)
The text was updated successfully, but these errors were encountered: