Ironclad / Ironclad/rivet

[Feature]: add support for templates in in HTTP headers & body (and perhaps in general)

Open
#285 2 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### Feature Request

It should be pretty obvious what I was trying to do here:

![image](https://github.com/Ironclad/rivet/assets/103348/a92ad20a-c663-4c52-a758-26dbad70d8da)

I figured putting `{{var_name}}` in e.g. Headers or Body inputs would cause an input to show up, so I could connect it to context.

Of course, there's pretty natural workaround, just use a text node:

![image](https://github.com/Ironclad/rivet/assets/103348/aa0c0222-0081-4507-89d2-5fd2b4a3719a)

It's just slightly less convenient - it would be nice if you didn't need to manually template outside of the HTTP call block to achieve this.

In fact, wouldn't it be nice if this feature just worked consistently everywhere, with any text input? 🙂

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.