-
Notifications
You must be signed in to change notification settings - Fork 260
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
.When(...).Throws gives a CouldNotSetReturnDueToNoLastCallException #803
Comments
304NotModified
changed the title
When Throws gives a CouldNotSetReturnDueToNoLastCallException
.When(...).Throws gives a CouldNotSetReturnDueToNoLastCallException
Apr 30, 2024
I think adding |
dtchepak
pushed a commit
that referenced
this issue
Jun 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This is of course a bug in the user code, as we should use
Throw
instead ofThrows
. But the exception is at least not clearAnd it's confusing, IntelliSense in VS 2022 also suggest throws:
To Reproduce
See #802
Expected behaviour
Environment:
Additional context
The analyzer gives a error, but that one is still a bit confusing
There are multiple options:
WhenCalled
(not sure if this is a binary breaking change?)void
The text was updated successfully, but these errors were encountered: