nightingale-rest-api-client icon indicating copy to clipboard operation
nightingale-rest-api-client copied to clipboard

[Feature request] Request chaining (not just variable chaining)

Open dpaulino opened this issue 4 years ago • 5 comments

Basically, trigger a request before or after a particular request is sent.

dpaulino avatar Nov 17 '20 00:11 dpaulino

Related to a comment in #144

dpaulino avatar Nov 17 '20 00:11 dpaulino

Ahhh... This explains why my later requests having difficulties with false tokens :D

It would be nice if the requests were made one after another when I put them into a collection. Alternatively, that could be an option in or an extra button next to the "Execute All" button. image

larsschellhas avatar Jan 25 '21 13:01 larsschellhas

@larsschellhas

It would be nice if the requests were made one after another when I put them into a collection

Can you clarify what you mean by this? Currently, nightingale should be executing them one after another if you do click "execute all" from the collection page. Are you saying it does not execute one after the other for you?

dpaulino avatar Feb 03 '21 06:02 dpaulino

Hey @dpaulino, sorry, if my description was not clear enough! Let me try again :) I figured out what the real problem is and will create a new issue for it.

larsschellhas avatar Feb 04 '21 12:02 larsschellhas

I have the same problem I send a POST request from which I update the id variable Then I want to send a deletion request by this id, if I do it via execute all, then the deletion request does not work And if you manually take turns, then everything is fine

fefemf10 avatar Nov 04 '23 13:11 fefemf10