Implement spec-level isolation for HttpStub interceptors#2334
Merged
joelrosario merged 4 commits intomainfrom Mar 18, 2026
Merged
Implement spec-level isolation for HttpStub interceptors#2334joelrosario merged 4 commits intomainfrom
joelrosario merged 4 commits intomainfrom
Conversation
- Add simple tests for the same
- Add simple tests for the same - Global interceptors will be applied first followed by matching specLevel interceptors
Summary
|
- Apply specLevel interceptors before global interceptors - Update tests accordingly
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What: Implement spec-level isolation for HttpStub interceptors
Why: Config V3 enables spec-level isolation for defining adapters, in contrast to V2, where all hooks were treated as global. This PR fixes HttpStub to permit isolation on a per-spec basis to work with V3
Checklist: