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
Describe the bug
When adding multiple interactions to the same endpoint using the onCall property of the response object we are obliged to add a status to the upperscope of the request. It's firstly counterintuitive and secondly not stated in the documentation (link)
To Reproduce
Steps to reproduce the behavior:
Add a mock with consecutive calls
stick to the documentation code
see the typescript compiler crying
Expected behavior
A different type for onCall behavior that do not need an upper scope status property.
Something that match the documentation
Screenshots
If applicable, add screenshots to help explain your problem.
Software (please complete the following information):
OS: [e.g. Windows] Mac os
NodeJS Version [e.g. 14] 20.15
Test Runner [e.g mocha] Jest 29.7
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When adding multiple interactions to the same endpoint using the
onCall
property of theresponse
object we are obliged to add a status to the upperscope of the request. It's firstly counterintuitive and secondly not stated in the documentation (link)To Reproduce
Steps to reproduce the behavior:
Expected behavior
A different type for
onCall
behavior that do not need an upper scopestatus
property.Something that match the documentation
Screenshots
If applicable, add screenshots to help explain your problem.
Software (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: