feat(size/XXL):Show the effective request (inherited auth, headers, and variables) on the request page - #15
Merged
arpit-bruno merged 5 commits intoJul 29, 2026
Conversation
sundram-bruno
approved these changes
Jul 29, 2026
arpit-bruno
approved these changes
Jul 29, 2026
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.
Problem
The request page should show the complete effective request so a reader understands exactly what the request sends. Today it does not surface config the request inherits from its collection or a parent folder. Auth and headers inherited from the collection/folder are not shown, and inherited variables are not shown either. In some cases the page shows "No request configuration" even though the request does have auth (and other config) inherited from its parent. The reader ends up with an incomplete or misleading picture of the request.
Proposed Solution
On the request page, will show the effective request by including what it inherits from the nearest parent (folder, then collection), clearly labeled as inherited:
Auth inherited from the collection/folder, with an inherited label.
Headers inherited from the collection/folder, alongside the request's own.
Variables inherited from the collection/folder (pre-request and post-response), alongside the request's own.
The inherited label names the specific source, for example "Inherited from Config" or "Inherited from Collection Config", and is a clickable link that navigates to that folder or collection page.
BRU - 4004