-
-
Notifications
You must be signed in to change notification settings - Fork 768
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
current state of setter/getter spies #2160
Comments
Well spotted. If you have any chance to do a forensic of this by using I don't know/remember, but you might be right that it's accidental. |
714911e#diff-2969afd226e75d3e2d257a1ab427d503 but no obvious reason why also, do you know what the return type is? a spy? or a descriptor containing spies? edit: looks like |
Something mysterious has been going on. I have hunch to what it is. The link you posted to the commit shows the diff for the generated docs for the latest version. That is always generated from |
And here it is: https://github.com/sinonjs/sinon/commits/714911ee19f237f7b5ef10d04ba3afb4b1c705a5/docs/_releases/latest/spies.md. It shows the PR #1976 by @salomvary added this section to the generated docs, not the source, and we were unable to catch it. Would you like to reintroduce them, @43081j? |
And with regards to return types you seem to be right. In the case of using |
great, thanks for looking into it. i was fixing up the typescript types, turns out they've been wrong for some time 🙈 PR is open anywho |
7.2.3:
https://sinonjs.org/releases/v7.2.3/spies/#using-a-spy-to-wrap-property-getter-and-setter
7.2.4 and onwards don't have this section of the docs.
For a patch release to remove a piece of functionality would be very questionable in terms of versioning so i assume the logic is still there in the source.
However, can someone please clear up what the situation is?
Maybe the docs just went walkies by accident?
The text was updated successfully, but these errors were encountered: