Dynamic Headers

[pawel-dubiel]

It would be great if we could create dynamic headers.

for example, some APIs may use a nonce and then based on the nonce we would need to create the hash and also update headers with that hash.

[aeeed99]

I like this idea, but I think it can be broken into a few features.

First step is adding a way to interpolate variables into the request (which would actually make them dynamic)

While there could be a few built-in variables, it would make sense to have a "pre-request" script that sets additional variables.

The example OP gives implies chaining requests, with subsequent ones having access to bindings for data returned from the previous request. This would be really cool and convenient, but is a larger feature to build out for sure.

I'll start by looking into an option for pre-request script/adding variables in requests.

[saphal1998]

@nickpalenchar Really new to contributing. Can you rope me in while working on this issue? I'd really like to learn.

[aeeed99]

Hi @saphal1998 I just emailed you, happy to work with you on this!

[sblasa]

Hi @nickpalenchar and @saphal1998 ! Just wondering if I could assist with this issue? I wasn't sure if @saphal1998 was working on it based on the status. Thanks!

[liyasthomas]

@sblasa you want to work on this feature? Shall I assign this to you.

[sblasa]

@liyasthomas , yes, I would like to work on this feature, but I'd like to work with @nickpalenchar 's implementation of the features he mentioned to help me get started.

[liyasthomas]

Great! Please collaborate and discuss! 🎉

[sblasa]

Thanks, @liyasthomas -- oh forgot to ask if you could also assign this to me.

[aeeed99]

Awesome @sblasa! I’ll be emailing you in a few hours 🙏

[aeeed99]

oops, @sblasa, I see you don't have a public email; go ahead and send me one instead (email address on my github profile). Talk soon!

[liyasthomas]

Environment variables feature branch is in WIP here: https://github.com/terranblake/postwoman/tree/terranblake/basic-environment

[aeeed99]

uh oh.. this is also being worked on here: https://github.com/liyasthomas/postwoman/tree/feature/dynamic-headers

Not sure how to proceed.

[liyasthomas]

You can go on as in your previous plans. Only one might be able to merge. Just shared another branch to see his implementation.

[NBTX]

This could also be merged with #139 potentially #196 and this use case of #147 was specifically mentioned here: #147 (comment)

[liyasthomas]

#147 (introducing environment variables) will most probably solve all these. @terranblake is working on it, and will make PR within few days.

[NBTX]

Okay in that case, I'll open a new issue in place of #139 and #196 about some kind of scripting language and we can close this PR in favor of working on #147 collectively (it doesn't really make sense to have two sets of people working on the exact same feature).

[liyasthomas]

Okay. Thats fine. Lets hear from @nickpalenchar about latest updates.

[aeeed99]

The work I've been doing with feature/dynamic-headers probably satisfies #139 more accurately, since its incorporating something similar to Postman's Pre-Request Scripts. This work could be moved to the new issue @NBTX plans to open in place of #139 and #196 , and I can continue there. It's been a very busy few weeks for me so my work's been slow to progress, but I'm hoping I'll be able to push this weekend and have it completed. When done, it can probably used in conjunction with #147

Additionally, @sblasa is looking at some syntax highlighting for pre-request scripts (potentially other places too); we might want to make that a separate issue for that as well

[liyasthomas]

Closing due to inactivity