New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature suggestion: allow "manual" (or step-by-step) chaining of the requests #31
Comments
This is exactly right. It might be possible to add another arg, like A simpler option is not sharing memory across Requester calls, but serializing response object with something like I think this is an edge case, but would be valuable for "exploratory runs" as you suggest. PR welcome |
The docs specify how to chain requests:
or
The problem is that you have to:
⌘⇧P
andReuqester: Run Requests Serially
.If you want to run them one-by-one you'll get:
I think I understand why is the --
env
is per run if you run the requests one by one then the second run has a separate env, without theResponse
.It would be nice to allow some form of persistent for such exploratory runs when you just prefer to run the script one-by-one. What do you think?
The text was updated successfully, but these errors were encountered: