fix throws().callsFake() precedence #2497
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose (TL;DR) - mandatory
Fixes #2496 by cleaning any previous
exception*
behavior whencallsFake
is used.Background (Problem in detail)
Precedence among behaviors is defined by the behavior itself (cleaning other previously set behaviors) and by the order at invocation time.
Since
throws
behavior (exception
andexceptionHandler
) is the first one to run at invocation time, other behaviors can only define precedence on its own definition. That's why I modifiedcallsFake
behavior to cleanthrows
Solution
When
callsFake
is chained on a stub it cleans previousexception
andexceptionHandler
values which essentially invalidates any previousthrows
orthrowsException
behaviours.Note: I think this fix should not break any current usage, because any attempt to run the stubbed function would have raised an exception already and the developer would have noticed the same I did notice: callsFake was ignored, so that, probably they applied some workaround like restoring + callsFake OR recreating the stub + callsFake.
How to verify - mandatory
Run:
You should see:
Checklist for author
npm run lint
passes