Repository navigation
Conversation
sansynx
force-pushed
the
fix/preserve-response-headers
branch
from
October 7, 2026 09:30
8212ae8 to
43e0087
Compare
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.
Summary
Preserve declared response headers in the OpenAPI resolver, including referenced responses, referenced headers, and header schema references
While investigating cloudflare/forge#20, I found that the Stream TUS operation correctly declares its upload URL in the
Locationresponse header.extractResponsescurrently drops the entire headers map, so downstream generators cannot discover itThis adds optional header metadata without changing the shape of responses that have no declared headers. The CLI integration is separate, this change alone does not fix the command
Validation
AI assistance was used for implementation and validation