Folder-level Variables & Scripts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 49
- Forks
- 26
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 4
Description
ℹ️ This issue was partially AI-generated and may contain technical inaccuracies.
Is your feature request related to a problem? Please describe.
Variables and pre/post scripts can only be defined at the collection level. A sub-group of requests that shares setup logic must repeat it on every request.
Describe the solution you'd like
Allow variables and pre/post scripts to be defined at the folder level and inherited by nested folders/requests, with the usual override precedence (request > folder > collection).
Describe alternatives you've considered
Duplicating variables/scripts per request; flattening everything to the collection level.
Additional context
Needs a clear resolution order. Relates to the existing variable system and scripting support (#580, #710).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing variable system and scripting support referenced in #580 and #710, focusing on how collection-level values and pre/post scripts are handled. Define and document resolution across nested folders and requests, including request > folder > collection precedence. Done means folder inheritance and overrides work consistently for variables and scripts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100