add removeInterceptorByPredictor to make interceptor removal logics customizable #2141
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.
Current approach requires to give the actual interceptor or the options used in preset mocks.
But in real world it's not always that easy to retrieve those info as input of removeIntercetor() (e.g cucumber style)
So here I opened up a new path to enable customizable removal logic for user, let them programmatically decide which interceptor to remove.
Dear mainteners please help to check this PR. thanks.
@mastermatt