Uh oh!
There was an error while loading. Please reload this page.
bugix: support min_calls and max_calls in expect_request! - #20
Conversation
Pull Request Test Coverage Report for Build 5d35ac68ab997a9da3b5f74eca58a6cd4d2102e1-PR-20Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This PR fixes
min_callsandmax_callsoptions forexpect_request!. These options were documented but completely ignored by the code. Max was taken fromcallsoption, min value was hardcoded to 1.The fix:
max_callsis explicitly provided: use itmin_callsis provided: usecalls(for backwards compatibility), ifcallsnot provided either, setmax_callstomin_callsvalue to avoid a clash