feat: support capturing and emitting header values#27
Merged
Conversation
ClaireDavis
approved these changes
Jan 15, 2026
ClaireDavis
left a comment
ClaireDavis
left a comment
Contributor
There was a problem hiding this comment.
domain lgtm
platform lgtm
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
3 participants
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.
📰 Summary of changes
This PR adds support for delivering response headers via the event listener system, enabling consuming applications to capture cookies and security headers for subsequent requests.
Functional changes:
New
RequestCompletedevent. This replacesMutativeRequestSuccessand:shouldTriggerDataMutationfor consumers who need the previous mutation-tracking behaviorMutativeRequestSuccesshas been removed and replaced withRequestCompleted🧪 Testing done
Unit tests were added for this functionality. Note: Because the primary test file was becoming unwieldy and didn't really follow a lot of our testing best practices (like test state isolation), we broke out a new test file rather than lumping into that one. In a future PR, I want to refactor the existing test file to break it into manageable chunks.