feat: add server timing to responses #164
Open
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.
Title
feat: add server timing to responses
Description
This PR adds server timing headers to responses by wrapping all responses returned by
fetch
in aResponse
object that includes the server timing headers.The headers are generated by wrapping async functions with a
serverTiming
utility function that records the time taken to execute the function, and then adding those headers to an array on the VerifiedFetch class.Notes & open questions
serverTiming
utility function usage so that it's easier to add new timings without having to handle the error and success cases manually for each one.Example of current server timings for http://bafybeie4vcqkutumw7s26ob2bwqwqi44m6lrssjmiirlhrzhs2akdqmkw4.ipfs.helia-sw-gateway.localhost/:
Example of current server timings for http://blog-ipfs-tech.ipns.helia-sw-gateway.localhost/:
Change checklist