{"action":"created","issue":{"url":"https://api.github.com/repos/mjackson/expect/issues/144","repository_url":"https://api.github.com/repos/mjackson/expect","labels_url":"https://api.github.com/repos/mjackson/expect/issues/144/labels{/name}","comments_url":"https://api.github.com/repos/mjackson/expect/issues/144/comments","events_url":"https://api.github.com/repos/mjackson/expect/issues/144/events","html_url":"https://github.com/mjackson/expect/issues/144","id":167918176,"number":144,"title":"Remove spy.reset","user":{"login":"mjackson","id":92839,"avatar_url":"https://avatars.githubusercontent.com/u/92839?v=3","gravatar_id":"","url":"https://api.github.com/users/mjackson","html_url":"https://github.com/mjackson","followers_url":"https://api.github.com/users/mjackson/followers","following_url":"https://api.github.com/users/mjackson/following{/other_user}","gists_url":"https://api.github.com/users/mjackson/gists{/gist_id}","starred_url":"https://api.github.com/users/mjackson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mjackson/subscriptions","organizations_url":"https://api.github.com/users/mjackson/orgs","repos_url":"https://api.github.com/users/mjackson/repos","events_url":"https://api.github.com/users/mjackson/events{/privacy}","received_events_url":"https://api.github.com/users/mjackson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-07-27T18:04:42Z","updated_at":"2016-07-27T19:34:12Z","closed_at":null,"body":"The meaning of `spy.reset` is ambiguous (see discussion in #138). What exactly does it reset? The call count? The return/thrown values?\r\n\r\nMy vote is to either remove it or make its meaning more clear. If we remove it, the simple upgrade path is to substitute all uses of `spy.reset()` with `spy.calls = []`. Super easy."},"comment":{"url":"https://api.github.com/repos/mjackson/expect/issues/comments/235695076","html_url":"https://github.com/mjackson/expect/issues/144#issuecomment-235695076","issue_url":"https://api.github.com/repos/mjackson/expect/issues/144","id":235695076,"user":{"login":"mjackson","id":92839,"avatar_url":"https://avatars.githubusercontent.com/u/92839?v=3","gravatar_id":"","url":"https://api.github.com/users/mjackson","html_url":"https://github.com/mjackson","followers_url":"https://api.github.com/users/mjackson/followers","following_url":"https://api.github.com/users/mjackson/following{/other_user}","gists_url":"https://api.github.com/users/mjackson/gists{/gist_id}","starred_url":"https://api.github.com/users/mjackson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mjackson/subscriptions","organizations_url":"https://api.github.com/users/mjackson/orgs","repos_url":"https://api.github.com/users/mjackson/repos","events_url":"https://api.github.com/users/mjackson/events{/privacy}","received_events_url":"https://api.github.com/users/mjackson/received_events","type":"User","site_admin":false},"created_at":"2016-07-27T19:34:12Z","updated_at":"2016-07-27T19:34:12Z","body":"It looks like proxyquire is using sinon for its spies implementation. Besides, seems like in the case you describe proxyquire would be creating incidental complexity and forcing me to handle it. Feels like a leaky abstraction."}}
{"actor":{"display_login":"mjackson"}}