Add support for merging header-timers with existing Server-Timing headers #2
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.
[note from tbeseda (the rest is Copilot): I'm testing out Copilot Workspace trial]
Related to #1
Adds support for merging
header-timers
values with existing Server-Timing headers without overwriting, and updates documentation and tests accordingly.mergeWithExisting
method inindex.js
that allows mergingheader-timers
values with existing Server-Timing headers, supporting both string and object formats for existing headers.toObject
method to facilitate merging by handling existing headers passed as either a string or an object, including cases where the Server-Timing header is already present.README.md
file with a new section and examples on how to use themergeWithExisting
method for mergingheader-timers
values with existing Server-Timing headers.index-test.js
to verify the correct functionality of themergeWithExisting
method, including tests for merging with existing headers provided as both strings and objects.For more details, open the Copilot Workspace session.