CodeShellDev / CodeShellDev/secured-signal-api
Allow `@VAR|#VAR` during Query / Path templating
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 39
- Forks
- 6
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 4
Description
Description
Currently you can only use variables for templating the path or query: /{{.NUMBER}}?text_mode={{.TEXT_MODE}}.
It could be useful to have access to headers and the body too...
Solution
Give the templater context with headers and body, basically doing the same thing as already done with body templating.
Contributor guide
No contributing guide indexed for this repository
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 locating the existing body-templating implementation and the code that templates path and query values. Trace how the templater receives its context, then determine how headers and body should be exposed for @VAR|#VAR usage. Done means the requested contexts work consistently with the existing path, query, and body templating behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100